System and method for transferring a timeshare property

ABSTRACT

The present disclosure provides a computer-executable method for executing a web-based program for producing a title transfer document. The method includes sending an instruction to an electronic device to request a type of transaction to be executed, wherein the type of transaction includes at least a removal of a current owner from the title or changing ownership to a new party. The method also includes receiving a communication from the electronic device in response to the request and executing a plurality of modules for requesting information about the timeshare property, the fees associated with the timeshare property, and at least one party of the transaction. The method further includes receiving input data in response to the executing step, linking the input data with at least one identifier in a document template, and producing the title transfer document upon completion of the linking step.

RELATED DISCLOSURES

The present application is a continuation of U.S. patent applicationSer. No. 14/259,708, filed on Apr. 24, 2014, which claims the benefit ofU.S. Provisional Patent Application Ser. No. 61/815,389, filed on Apr.24, 2013, and U.S. Provisional Patent Application Ser. No. 61/902,462,filed on Nov. 11, 2013, which are hereby incorporated by reference intheir entirety.

FIELD OF THE DISCLOSURE

The present disclosure relates to a system and method for transferringproperty, and in particular to a system and method for producing atransfer document for transferring timeshare property.

BACKGROUND

A timeshare is a property with a particular form of ownership or usagerights. In particular, the rights to this type of property can be heldby multiple parties with designated periods of time in which each partyhas priority to use their rights to occupy the property. This can oftenbe in the form of days, weeks, etc. and may take place at the same timeeach year. In other words, an owner of a timeshare property may haverights to the property for the same week in April each year. Theproperty rights, however, do not grant ownership to the property butrather only rights to use for the allotted period of time.

When a seller desires to sell his or her right to the timeshare, thesale is generally treated as real property and can be sold to anotherparty. Many of the processes for transferring rights to a timesharerequire significant time and money to complete.

SUMMARY

In a first embodiment of this disclosure, a computer-executable methodis provided for producing a title transfer document for transferring atimeshare property. The method includes providing a program thatincludes a set of instructions executable by an electronic computingdevice; executing a resort property module of the program, the resortproperty module being executable to request information including thetype of transaction being executed, resort name associated with thetimeshare property, owner number associated with the timeshare property,a unit number associated with the timeshare property, and a designatedweek associated with the timeshare property; executing a partyinformation module stored in the program, the party information modulebeing executable to request information about a current owner, a newowner, and how title will vest upon completion of the transfer;executing a documentation module stored in the program, thedocumentation module being executable to receive any document from thecurrent owner or new owner related to the transfer; executing a paymentmodule stored in the program, the payment module requesting informationabout purchase price and any fees due associated with maintenance fees;receiving input data from each of the modules; locating a documenttemplate including at least one identifier; linking the input data withthe at least one identifier in the document template; and producing atitle transfer document from the at least one document template fortransferring the title of the timeshare property.

In one example of this embodiment, the execution of each module includeselectronically downloading a predefined screen layout to the electroniccomputing device for requesting the input data. In a second example, themethod includes storing the input data as a transaction file on a serveror in a database. In a third example, the method includes displaying anapplication status bar on a screen of the electronic computing deviceduring the execution of each module. In a fourth example, the methodincludes requesting user identification and acknowledgement of a set ofconditions for starting an application process before the executing aresort property module. In a fifth example, the method includesreceiving a user identification from the electronic computing device;communicating with a server or database for a file associated with theuser identification; and displaying contents of the file on a screen ofthe electronic computing device, wherein the contents include at leastone unfinished or finished application.

In a sixth example, the executing a resort property module includesrequesting whether a power of attorney document will be used by at leastone party of the transaction. In a seventh example, the executing aparty information module includes requesting if the current owner andnew owner includes more than one person or company. In an eighthexample, the method includes executing an address verification moduleduring or after the execution of the party information module, theaddress verification module being executable to verify an address of atleast one of the current owner and new owner with a third party addresssystem. In a ninth example, the locating step comprises locating areview application template from a template library stored on a serveror in a database, the review application template including a pluralityof identifiers positioned within the template, linking each of theplurality of identifiers in the review application template with theinput data, producing a review application file from the reviewapplication template, and displaying the review application file on ascreen of the electronic computing device.

In a second embodiment, a computer-executable method is provided forexecuting an electronic program stored on a server for producing a titletransfer document in a timeshare property. The method includesrequesting a user identification to enable the program for executing aset of instructions stored on the server, where the set of instructionsform part of the program; receiving the user identification andrequesting a file stored on the server or database that is in electroniccommunication with the program, the file being associated with the useridentification; sending an instruction to an electronic device torequest a type of transaction to be executed, wherein the type oftransaction includes at least a removal of a current owner from thetitle or changing ownership to a new party; receiving a communicationfrom the electronic device in response to the request; executing aplurality of modules for requesting information about the timeshareproperty, fees associated with the timeshare property, and at least oneparty of the transaction; receiving input data in response to theexecuting step; merging the input data with at least one identifier in adocument template; and producing the title transfer document uponcompletion of the merging step.

In one example of this embodiment, the executing step includes executinga start application module to request information about a developer ofthe timeshare property; executing a resort property informationcollection module, the resort property information collection modulebeing executable to request information about a resort where thetimeshare property is located and an owner number; executing a titletype module, the title type module being executable to requestinformation about transfer options, title insurance, unit number, andweek number; executing an owner information module, the ownerinformation module being executable to request information about a nameof an owner, marital status, address, and contact information of theowner; executing a documentation module stored in the web application,the documentation module being executable to request any documentcorresponding to the transfer; and executing a payment module stored inthe web application, the payment module requesting information aboutpurchase price and any fees due associated with maintenance fees.

In a second example, the method includes executing an addressverification module during or after the execution of the ownerinformation module, the address verification module being executable toverify an address of at least one of a current owner and a new owner. Ina third example, the method includes storing the input data in atransaction file in the web application, on the server, or in thedatabase. In a fourth example, the method includes displaying anapplication status bar on a screen of the electronic device during theexecution of each module.

In a third embodiment, a web-based program is stored on a server andexecutable over a network by an electronic computing device to producetitle transfer documents for closing a transfer of timeshare property.The web-based program includes a set of instructions for executing aplurality of modules for requesting information about the timeshareproperty and each party involved in the transfer of the timeshareproperty; receiving input data from each of the plurality of modules;assigning the input data to predefined identifiers; determining whichtitle transfer documents are necessary for closing the transfer based onthe input data; locating document templates in a template library storedon the server in response to the determining step; and executing adocument generation module, the document generation module beingexecutable to identify the predefined identifiers in each documenttemplate, assign input data to each predefined identifier in eachdocument template, and produce the title transfer documents from thecompleted document templates.

In one example of this embodiment, the title transfer documents includeat least one of a resort transfer form, sale contract, buyer checklist,seller checklist, file cover page, third party transaction agreement,compliance and correction agreement, authorization to releaseinformation to a title company form, certificate of trust document,attorney in fact affidavit, name affidavit, fees due notice, continuousmarriage affidavit, and limited liability company affidavit. In a secondexample, the set of instructions includes requesting a useridentification to enter a web portal for executing the web-basedprogram; receiving the user identification; and sending an instructionto the server or database to locate a file associated with the useridentification stored on the server. In a third example, the set ofinstructions includes storing the input data as a transaction file onthe server or in the database, the transaction file being associatedwith the user identification. In a fourth example, the process includesexecuting an order estoppel module to request an estoppel.

In a fourth embodiment of this disclosure, a method is provided formodifying a package of documents for transferring a timeshare property.The method includes providing a first server disposed in electricalcommunication with a second server and a database, the first server andsecond server arranged so that instructions are transferabletherebetween for a plurality of operations, and the second serverelectrically coupled to a computing device including a processor and adisplay screen; providing a template library electronically stored onthe database; storing a first plurality of templates in the templatelibrary; receiving by the first server a first instruction from thesecond server to access an application profile for a particulardeveloper or resort company of timeshare properties; receiving by thefirst server a second instruction from the second server to add atemplate to a package stored on the first server or database, thepackage including one or more templates from the first plurality oftemplates; sending a list of the first plurality of templates by thefirst server to the second server; receiving by the first server fromthe second server a third instruction associated with a selection of atleast one of the first plurality of templates; modifying the package bythe first server to include the at least one selected template from thefirst plurality of templates to the package, wherein the packagecomprises a second plurality of templates after the modifying step; andsending the modified package by the first server to the second server,wherein the package of the second plurality of templates are executableto produce a package of documents for transferring the timeshareproperty.

In one example of this embodiment, at least one of the first pluralityof templates comprises an identifier. In a second example, the methodincludes receiving a fourth instruction by the first server from thesecond server corresponding to an identification of a developer orresort company site. In a third example, the method includes receiving afourth instruction by the first server from the second servercorresponding to an identification of a title processing company. In afourth example, the method includes accessing by the first server aplurality of standard packages stored on the first server, secondserver, or the database. In a fifth example, the plurality of standardpackages comprises a third plurality of templates, the third pluralityof templates being executable to produce one or more documents fortransferring the timeshare property.

In another embodiment, a method is provided for producing a package ofdocuments for transferring a timeshare property. The method includesproviding a first server disposed in electrical communication with asecond server and a database, the first server and second serverarranged so that instructions are transferable therebetween for aplurality of operations; providing a template library electricallystored on the database; storing a first plurality of templates in thetemplate library and a plurality of packages on the first server or thedatabase; receiving by the first server a first instruction from thesecond server to add a new package to the plurality of packages; sendingby the first server to the second server a request for a new packagename; receiving by the first server the new package name from the secondserver; receiving by the first server a second instruction from thesecond server to edit a template list of the new package; sending by thefirst server to the second server a list of the first plurality oftemplates for adding to the new package; receiving by the first server athird instruction from the second server to add at least one of thefirst plurality of templates to the new package; and storing the newpackage with the at least one of the first plurality of templates addedthereto on the first server or the database.

In one example of this embodiment, the method includes receiving by thefirst server a fourth instruction from the second server to retrieve theplurality of packages from the database. In a second example, the methodincludes accessing by the first server the plurality of packages fromthe database. In a third example, the method includes sending a fourthinstruction by the first server to the second server, where the fourthinstruction corresponds to an option to remove one template of the firstplurality of templates from the database.

In a different embodiment of this disclosure, a method is provided ofproducing a template for a document to transfer a timeshare property.The method includes providing a first server disposed in electricalcommunication with a second server and a database, the first server andsecond server arranged so that instructions are transferabletherebetween for a plurality of operations; providing a template libraryelectrically stored on the database; storing a first plurality oftemplates in the template library and a plurality of packages on thefirst server or the database; receiving by the first server a firstinstruction from the second server to execute a new template module;sending by the first server to the second server a list of the firstplurality of templates and an option to add a new template or downloadone of the plurality of first templates; receiving by the first serverfrom the second server a new template name for adding a new template tothe first plurality of templates; receiving by the first server a secondinstruction from the second server to upload a file associated with thenew template name, the file being stored on the second server;determining if the file includes a file name identical to the newtemplate name; uploading the file if the file name is identical to thenew template name; and storing the file so that a second plurality oftemplates are stored in the database.

In one example of this embodiment, the method includes storing the filein the template library. In a second example, the method includessending a third instruction by the first server to the second serverwhere the third instruction corresponds to a template form. In a thirdexample, the template form comprises a request for a new template name.In a fourth example, the method includes storing the new template namein the template library before the second instruction is received by thefirst server. In a fifth example, the method includes sending a thirdinstruction by the first server to the second server corresponding to anoption to upload a file associated with the new template name.

In a sixth example, the method includes receiving by the first server athird instruction from the second server to add a template to a packagestored on the first server or database, the package including one ormore templates from the second plurality of templates. In a seventhexample, the method includes sending a list of the second plurality oftemplates by the first server to the second server; and receiving by thefirst server from the second server a fourth instruction associated witha selection of at least one of the second plurality of templates. In aneighth example, the method includes modifying the package by the firstserver to include the at least one selected template from the secondplurality of templates to the package. In a ninth example, the methodsending the modified package by the first server to the second server,wherein the package includes a third plurality of templates which areconfigurable to produce a package of documents for transferring thetimeshare property.

BRIEF DESCRIPTION OF THE DRAWINGS

The above-mentioned aspects of the present disclosure and the manner ofobtaining them will become more apparent and the disclosure itself willbe better understood by reference to the following description of theembodiments of the disclosure, taken in conjunction with theaccompanying drawings, wherein:

FIG. 1 is a system diagram of one embodiment of the present disclosure;

FIG. 2 is another system diagram of a hardware and software arrangementfor implementing, accessing, or executing a process as disclosed herein;

FIG. 3 is a flow diagram of one embodiment of the disclosure;

FIG. 4 is a schematic of a login screen;

FIG. 5 is a schematic of a screen for registering an account;

FIG. 6 is a schematic of a screen for starting a new transferapplication;

FIG. 7 is a schematic of a screen for requesting resort propertyinformation;

FIG. 8 is a schematic of a screen for requesting information regardingtitle type and number of units and weeks;

FIG. 9 is a schematic of a screen for requesting information about acurrent owner;

FIG. 10 is a schematic of a screen for requesting information about anew title;

FIG. 11 is a schematic of a screen for requesting documentation forcompleting a transaction;

FIG. 12 is a schematic of a screen for requesting notification settingsinformation;

FIG. 13 is a schematic of a screen for reviewing a transactionapplication and providing payment options;

FIG. 14 is a schematic of a screen for providing details after anapplication has been submitted;

FIG. 15 is another schematic of a screen for providing details after anapplication is submitted or saved before completion;

FIG. 16 is a schematic of a screen providing details of existingapplications for a given user or login credentials;

FIG. 17 is a schematic of a screen displaying status information of astored application;

FIG. 18 is a flow diagram of another embodiment of a process fortransferring a timeshare property;

FIG. 19 is of a screen for requesting resort property information;

FIG. 20 is a schematic of a screen for requesting information regardingtitle type and number of units and weeks;

FIG. 21 is a schematic of a screen for requesting information about anew owner;

FIG. 22 is a schematic of a screen for requesting information about anew title;

FIG. 23 is a schematic of a screen providing options for starting a newapplication, finishing an existing application, or checking a status ofa completed application;

FIG. 24 is a schematic of a screen for providing details of a transferapplication status;

FIG. 25 is a different embodiment of a process for preparing documentsand forms for a transfer application;

FIG. 26 is a schematic of an introductory or welcome letter as part of aclosing document package;

FIG. 27 is a schematic of a file cover page as part of a closingdocument package;

FIG. 28 is a schematic of a file checklist for a seller as part of aclosing document package;

FIG. 29 is a schematic of a file checklist for a buyer as part of aclosing document package;

FIG. 30 is a schematic of a third party transaction agreement as part ofa closing document package;

FIG. 31 is a schematic of a compliance and correction agreement as partof a closing document package;

FIG. 32 is a schematic of a resort transfer form as part of a closingdocument package;

FIG. 33 is a schematic of an additional purchaser form as part of aclosing document package;

FIG. 34 is a schematic of a contract document as part of a closingdocument package;

FIG. 35 is a schematic of an authorization to release information to atitle company as part of a closing document package;

FIG. 36A is a first portion of a schematic of a certificate of trustdocument as part of a closing document package;

FIG. 36B is a second portion of the schematic of FIG. 36A;

FIG. 37 is a schematic of an attorney in fact affidavit document as partof a closing document package;

FIG. 38 is a schematic of a name affidavit document as part of a closingdocument package;

FIG. 39A is a first portion of a schematic of a limited liabilitycompany affidavit document as part of a closing document package;

FIG. 39B is a second portion of the schematic of FIG. 39A;

FIG. 40A is a first portion of a schematic of a continuous marriageaffidavit document as part of a closing document package;

FIG. 40B is a second portion of the schematic of FIG. 40A;

FIG. 41 is a schematic of a fees due notice document as part of aclosing document package;

FIG. 42A is a first portion of a schematic of an owner/seller affidavitdocument as part of a closing document package;

FIG. 42B is a second portion of the schematic of FIG. 42A;

FIG. 43 is a flow diagram of a further embodiment of a method forreceiving a transfer application and processing the application tocomplete an overall transaction;

FIG. 44 is a flow diagram of one example of a process for executing arequest an estoppel application;

FIG. 45 is a schematic of a welcome screen module of the process of FIG.44;

FIG. 46 is a schematic of a start application module of the process ofFIG. 44;

FIG. 47 is a schematic of one block in the process of FIG. 44 forrequesting transaction information;

FIG. 48 is a schematic of one block in the process of FIG. 44 forrequesting information regarding estimated fee, unit(s), and week(s);

FIG. 49 is a schematic of one block in the process of FIG. 44 forexecuting a notification settings module;

FIG. 50A is a partial schematic of one block in the process of FIG. 44for displaying a review application template with information collectedin the process;

FIG. 50B is another partial schematic of one block in the process ofFIG. 44 for displaying a review application template with informationcollected in the process;

FIG. 51 is a flow diagram of another embodiment of a process forexecuting a hold an escrow application;

FIG. 52 is a flow diagram of executing a process for a rentalapplication as part of the process of FIG. 51;

FIG. 53 is a flow diagram of executing a process for a sale applicationas part of the process of FIG. 51;

FIG. 54 is a flow diagram of executing a process for a brokerapplication as part of the process of FIG. 51;

FIG. 55 is a schematic of a screen for requesting a type of applicationto complete;

FIG. 56 is a schematic of one block of the process of FIG. 52 forexecuting a start rental application module;

FIG. 57 is a schematic of one block of the process of FIG. 52 forrequesting transaction information;

FIG. 58A is a partial schematic of one block of the process of FIG. 52for providing a review rental application template with informationreceived during the process;

FIG. 58B is another partial schematic of one block of the process ofFIG. 52 for providing a review rental application template withinformation received during the process;

FIG. 59 is a schematic of one block of the process of FIG. 53 forexecuting a start sale application module;

FIG. 60 is a schematic of one block of the process of FIG. 53 forrequesting transaction information;

FIG. 61 is a schematic of one block of the process of FIG. 53 forproviding a review sale application template with information receivedduring the process;

FIG. 62A is a partial schematic of one block of the process of FIG. 51for providing application information for a given registered account;

FIG. 62B is another partial schematic of one block of the process ofFIG. 51 for providing application information for a given registeredaccount;

FIG. 63 is a schematic of one block of the process of FIG. 54 forrequesting transaction information;

FIG. 64A is a first portion of a schematic of one block of the processof FIG. 54 for providing a review broker application template withinformation received during the process;

FIG. 64B is a second portion of the schematic of FIG. 64A;

FIG. 65 is a process for executing a real estate transaction andgenerating the necessary transaction documents;

FIG. 66 is a schematic of one screen of the process of FIG. 65 fordisplaying applications associated with a registered login;

FIG. 67 is a schematic of one screen of the process of FIG. 65 forexecuting a sale information module;

FIG. 68 is a schematic of one screen of the process of FIG. 65 forrequesting co-broker information;

FIG. 69 is a schematic of one screen of the process of FIG. 65 forexecuting a resort information module;

FIG. 70 is a schematic of one screen of the process of FIG. 65 forexecuting a transaction information module;

FIG. 71 is a schematic of one screen of the process of FIG. 65 forrequesting reservation information;

FIG. 72 is a schematic of one screen of the process of FIG. 65 forexecuting a party information module;

FIG. 73 is a schematic of another screen of the process of FIG. 65 forexecuting a party information module;

FIG. 74 is a schematic of one screen of the process of FIG. 65 fordisplaying a review application template;

FIG. 75 is a schematic of one screen of the process of FIG. 65 forexecuting an application processing module;

FIG. 76A is a first portion of a schematic of one example of a netlisting agreement generated via execution of a document generationmodule of the process of FIG. 65;

FIG. 76B is a second portion of the schematic of FIG. 76A;

FIG. 77A is a first portion of a schematic of an assessment certificateand estoppel letter template;

FIG. 77B is a second portion of the schematic of FIG. 77A;

FIG. 78 is a schematic of a resale transfer agreement template;

FIG. 79 is a schematic of an escrow agreement template;

FIG. 80 is a system diagram of a different embodiment of the presentdisclosure;

FIG. 81 is a schematic of an application dashboard;

FIG. 82 is a schematic of a pending application dashboard;

FIG. 83 is a schematic of a developer or resort application dashboard;

FIG. 84 is another schematic of the application profile of FIG. 81;

FIG. 85 is a process for adding a package of documents for atransaction;

FIG. 86 is a process for modifying an existing package or adding a newpackage of documents for a transaction; and

FIG. 87 is a process for executing a new template module.

Corresponding reference numerals are used to indicate correspondingparts throughout the several views.

DETAILED DESCRIPTION

The embodiments of the present disclosure described below are notintended to be exhaustive or to limit the disclosure to the preciseforms disclosed in the following detailed description. Rather, theembodiments are chosen and described so that others skilled in the artmay appreciate and understand the principles and practices of thepresent disclosure.

Referring to FIG. 1, a conventional computer system 100 is provided forimplementing, accessing, and using various embodiments of the presentdisclosure. The computer system 100 is illustrated as part of anetworked computer system including one or more individual usercomputers 120, 140 and 160 (e.g., desktop or PC-based computers,workstations, etc.) coupled to a server 180 (e.g., a PC-based server, aminicomputer, a midrange computer, a mainframe computer, etc.) through anetwork 190. Network 190 represents a networked interconnection,including, but not limited to local-area, wide-area, wireless, andpublic networks (e.g., the Internet). Moreover, any number of computersand other devices may be networked through network 190, e.g., multipleservers. Each individual computer therefore can access the Internetthrough the network 190.

User computer 160, which may be similar to computers 120, 140, mayinclude a central processing unit (CPU) 162, a number of peripheralcomponents such as a computer display 164, a storage device 166, aprinter 168, and various input devices (e.g., a mouse 170, keyboard 172,microphone, camera, etc.) and output devices such as speakers (notshown). The computer server 180 may be similarly configured, albeit withgreater processing performance and storage capacity, as is well known inthe art.

FIG. 2 further illustrates a conventional hardware and softwareenvironment for an apparatus 200 suitable for implementing, accessing,or using one or more of the embodiments of the present disclosure. Forthe purposes of the disclosure, apparatus 200 may represent a computer,computer system or other programmable electronic device (e.g., mobilephone, PDA, laptop, etc.), including: a client or user computer (e.g.,similar to computers 120, 140 and 160 of FIG. 1), a server computer(e.g., similar to server 180 of FIG. 1), a portable computer, anembedded controller, etc. Apparatus 200 will hereinafter also bereferred to as a “computer,” although it should be appreciated the term“apparatus” may also include any other suitable programmable electronicdevice consistent with the disclosure.

Computer 200 can include at least one processor 210 coupled to a memory220. Processor 210 may represent one or more processors (e.g.,microprocessors), and memory 220 may represent the random access memory(RAM) devices comprising the main storage of computer 200, as well asany supplemental levels of memory, e.g., cache memories, non-volatile orbackup memories (e.g., programmable or flash memories), read-onlymemories, etc. In addition, memory 220 may be considered to includememory storage physically located elsewhere in computer 200, e.g., anycache memory in a processor 210, as well as any storage capacity used asa virtual memory, e.g., as stored within an information database 260 oron another computer coupled to computer 200 via network 280.

Computer 200 also may receive a number of inputs and outputs forcommunicating information externally. For interface with a user, thecomputer 200 may include one or more input devices 230 (e.g., akeyboard, a mouse, a trackball, a joystick, a touchpad, camera, and/or amicrophone, among others) and a display 240 (e.g., a CRT monitor, an LCDdisplay panel, and/or a speaker, among others). It should beappreciated, however, that with some implementations of computer 200,e.g., some server implementations, direct user input and output may notbe supported by the computer, and interface with the computer may beimplemented through client computer or workstation networked withcomputer 200.

For additional storage, computer 200 may also include one or more massstorage devices 260 configured to store an application or software-basedinstructions for performing a task. Exemplary devices 260 can include: afloppy or other removable disk drive, a hard disk drive, a direct accessstorage device (DASD), an optical drive (e.g., a CD drive, a DVD drive,etc.), and/or a tape drive, among others. Furthermore, computer 200 mayinclude an interface with one or more networks 280 (e.g., a LAN, a WAN,a wireless network, and/or the Internet, among others) to permit thecommunication of information with other computers coupled to thenetwork. It should be appreciated that computer 200 typically includessuitable analog and/or digital interfaces between processor 210 and eachof components 220, 230, 240, 260 and 280.

Computer 200 can be operated under the control of an operating system290, and executes various computer software applications, components,programs, objects, modules, etc. Moreover, various applications,components, programs, objects, modules, etc. may also execute on one ormore processors in another computer coupled to computer 200 via anetwork 280, e.g., in a distributed or client-server computingenvironment, whereby the processing required to implement the functionsof a computer program may be allocated to multiple computers over anetwork.

In general, the routines executed to implement one or more of theembodiments of the disclosure, whether implemented as part of anoperating system or a specific application, component, program, object,module or sequence of instructions will be referred to herein as“computer programs,” or simply “programs.” The computer programstypically comprise one or more instructions that are resident at varioustimes in various computer memory and storage devices. When a program isread and executed by a processor, the program causes the computer toexecute a module, a step, an instruction, or an element embodying thevarious aspects of the disclosure. In this disclosure, a “module” can beone or more instructions or steps that is executable to achieve a resultor a desired task. A “program” can include one or more “modules”, andeach “module” can be executed to request certain information, receivecertain information, or otherwise perform a certain operation.

Moreover, while the disclosure has and hereinafter will be described inthe context of fully functioning computers and computer systems, thoseskilled in the art will appreciate that the various embodiments of thedisclosure are capable of being distributed as a program product in avariety of forms, and that the disclosure applies equally regardless ofthe particular type of signal bearing media used to actually carry outthe distribution. Examples of signal bearing media include but are notlimited to recordable type media such as volatile and non-volatilememory devices, floppy and other removable disks, hard disk drives,optical disks (e.g., CD-ROM's, DVD's, etc.), among others, andtransmission type media such as digital and analog communication links.

In addition, various programs described hereinafter may be identifiedbased upon the application for which they are implemented in a specificembodiment of the disclosure. However, it should be appreciated that anyparticular program nomenclature that follows is used merely forconvenience, and thus the disclosure should not be limited to use solelyin any specific application identified and/or implied by suchnomenclature. As described above, in this disclosure one or moreembodiments may refer to a process, method, program, module, logic,algorithm or set of instructions to describe one or more actions beingexecuted. In each case, the process, method, program, module, logic,algorithm or set of instructions may execute one or more blocks, steps,or set of conditions, depending upon the process or program beingexecuted. This may include making calculations, executing a program orprocess within a larger program or process, or otherwise makingdeterminations to advance or return to previous blocks or steps. Acontrol system that includes a computing device such as a user computer,network, server, database, web-based program, etc. can execute eachprocess, method, program, module, logic, algorithm or set ofinstructions as necessary to complete a desired task. In otherinstances, the program, process, module, method, algorithm, etc. can bestored on a removable drive, including a CD, DVD, memory card, memorydisk, memory stick, or any other removable device capable to storing aprogram.

Referring to FIG. 3, for example, an embodiment of a method 300 forprocessing the transfer of a timeshare is provided. In this process ormethod 300, an owner of timeshare rights can access a computing devicesuch as a computer 160, mobile device, or the like and access anelectronic database 260 for initiating the process 300. In doing so, theowner may access a web portal (e.g., website or link) or other means foraccessing the database via block 302. The web portal, for example, maybe stored on a computer server 180 and accessible via a network 190, forexample. A web-based program, for example, may be accessed over theInternet to facilitate the execution of blocks set forth in process 300.Two examples of a web portal or application for executing this process300 can be found at http://www.Timeshareproplus.com andhttp://www.Closemytimeshare.com, the contents of both of which arehereby incorporated by reference. Moreover, the process 300 can bestored in a memory and include a set of instructions for execution by aprocess of the computer. An example of a web portal screen 400 is shownin FIG. 4.

The web portal 400 can be accessed by a user who enters a requisiteaddress in a web browser to access the Internet. The web address isunique to the web portal 400. As shown in FIG. 4, once the user entersthe required web address into a web browser, the web portal 400 can bedisplayed on the user's computer display, for example. The web portal400 can include and display a selectable link 402 for allowing aprevious, registered user to enter and access the database. In addition,a second selectable link 404 is displayed which can be selected foraccessing help or assistance with the web portal 400. A login box ordisplay 406 can be displayed on the web portal screen 400 as shown inFIG. 4 and include a first text box 408 and a second text box 410. Thefirst text box 408 can be selectable by a user such that text (e.g.,letters, numbers, symbols, etc.) can be entered therein. In the exampleof FIG. 4, an email address associated with a previous, registered usercan be entered in the first text box 408. The second text box 410 can besimilar to the first text box 408 such that a password or otheruser-identifiable code can be entered therein. The password or code canbe one created specifically by or for the registered user and is linkedor associated directly with the email address (or user identificationentered in the first text box 408). The email address or useridentification and password or code can be stored on a web server or ina database stored on the server. As such, this information may beretrievable by the system 100 each time a user attempts to enter thedatabase.

The web portal screen 400 can also display a selectable button 412,icon, or link for executing a login operation. By selecting the button412, the processor can request information from the server or databaseto determine whether the email address, user identification, user name,etc. and associated password or code can be located and identified to aregistered user. In the event a registered user is unable to rememberhis or her password, a selectable link 416 is displayed on the webportal screen 400.

In FIG. 4, the owner of the timeshare rights or a broker title companyrepresentative may be asked one or more questions related to theidentification of the owner. For instance, the owner may first create anaccount through the web portal. To do so, the web portal screen 400 candisplay a selectable link 414 for creating a user-identifiable accountor registration. The account can be a function of various criteria, suchas email address, name, location, or a user-identifiable login name. Theowner may further be asked to enter a unique password or code in theform of letters (lowercase, uppercase), numbers, symbols, etc.

An example of a registration screen 500 for setting up and registeringan account is provided in FIG. 5. Here, the screen 500 can display aplurality of selectable text boxes 502 for a user to enter information.For instance, the user may be asked for an email address, user name, orlogin name. In some instances, there may be requirements in terms of thenumber of letters (uppercase, lowercase), numbers, or symbols that formthe user name or login name. The user may also be asked to create apassword that is to be associated with the email address, user name, orlogin name. The system may have requirements for the password as well interms of length and type of characters (uppercase letter, lowercaseletter, number, symbol, etc.).

In one aspect of this embodiment, a broker handling a timeshare transfermay be required to setup a username and password. This may particularlybe the case for a broker who is handling multiple transactions or isrepresenting different owners or timeshare companies. In a buyer-sellertransaction without a broker involved, neither party may be required tocreate a username and password. In this instance, each party may onlyhave a single transaction and thus the process 300 may be executedwithout the need to log into the web portal 400. For purposes of thisembodiment, a broker is involved in the transaction and thus the brokermay be required to register an account or log into an existing accountin order to enable or advance the timeshare transfer application process300 of FIG. 3.

Once the various requirements are satisfied in the plurality of textboxes 502, the user (e.g., a broker in a transaction) can click orselect a selectable register button 504 as shown in FIG. 5. By selectingthis button, this information can be communicated over the server andsaved to a memory file in the database or some other location thatallows it to be located and retrievable if entered at another time viathe web portal screen 400. As also shown in FIG. 5, the registrationscreen 500 may also display a selectable login button which allows aregistered user to be directed to or redirected to the portal screen 400for logging into the database.

As previously described, once the broker or user creates an account, theweb-based program or system stored on the server 180 can executeinstructions to display a screen indicating the account has beenregistered. In addition to the registration complete screen, thenow-registered user can click a link to log into the timeshare transfersystem. The login screen can be similar to the one shown in FIG. 4 anddescribed above. In the event the user has forgotten his or herpassword, a link can be provided to assist with recovering saidpassword. Moreover, if the user has additional questions or needs help,a similar link 404 as shown in FIGS. 4 and 5 can be provided for theuser to receive assistance.

Once the user has logged into his or her account, the applicationprocess 300 is enabled or triggered to advance to display a screen 600similar to the one shown in FIG. 6. Here, the process 300 presents aplurality of questions to the user including the role of the user via adrop-down menu 602. The drop-down menu can include options such asseller, buyer, or transfer company. In other embodiments, additionalparties such as brokers, realtors, or other parties to a transfer may beable to log into the system.

Before the user can access the system, the process 300 further displaysa list of questions or requirements via the web-based program tocontinue. This list can include, for example, 1) all parties that arebeing listed on a title are of a certain age; 2) there are nooutstanding loans on the property; 3) all maintenance fees, taxes, anddues are paid and up-to-date; 4) user has read and understood theprivacy policy and terms of service; and 5) user has a signed purchaseand sales agreement as required by a timeshare resort. In the event oneor more of the conditions cannot or is not affirmed, the process 300 ofFIG. 3 cannot advance to block 304.

As shown, the privacy policy and terms of service can be stored in theweb-based program or on the server and are accessible via a selectablelink 606 displayed in the screen of FIG. 6. If clicked, a privacy policyor terms of service can be retrieved and displayed to the user. The usercan also be asked to select a developer or resort name from a drop-downmenu 608. This information can be downloaded to the server and list anyof a plurality of different developers. The list of developers from themenu 608 may change over time, and as it does, the menu will becontinuously updated. Once each box or requirement has been selected oraffirmed and a developer is selected from the drop-down menu 608, theprocess can advance once the “Start Application” button 610 is selected.

Once button 610 is selected, the web-based program advances within itsset of instructions to further execute the application process 300. Inblock 304, the process 300 can present one or more questions related tothe transaction and transfer. In FIG. 7, for example, a screen 700 maybe displayed to the user requesting information about the transactiontype (e.g., a transfer to a new owner, a company, charity, etc.). Here,the user can select one or more of the options from a selectable buttonor box 702. The screen 700 can once again show the name of thedeveloper, and from a drop-down menu 704 the process 300 can ask theuser to select a resort name. In at least one embodiment, the resortname corresponds to at least one or more resorts owned or managed by thedeveloper. If there are multiple transactions, the process 300 mayrequire the user to submit a new application for each transaction. Asshown in FIG. 7, an information button or icon 714 can be displayedwhich can provide additional details to the user if a mouse cursoreither is placed over the icon 714 or the icon is selected.

The process 300 may also request the owner's or seller's number that isassociated with the property being transferred. In FIG. 7, a text box706 can be displayed on the screen 700 such that the user can enter thisinformation therein. Moreover, depending on the type of transaction, apower of attorney may be required. A list of options may be displayed onthe screen 700 related to a power of attorney document. As shown, aselectable icon or button 708 can be provided on the screen 700 for theuser to select, where the option may correspond to neither buyer orseller are submitting a power of attorney form, only buyer is submittinga power of attorney form, or only the seller is submitting a power ofattorney form. In other aspects, the web-based program may be able toproduce a power of attorney document that is provided to the user viaemail or other known ways. The screen 700 can further display a continueor next button 710 that is selectable to advance from screen 700. Oncethe information requested by the process 300 is provided by the user,selection of the continue button 710 can advance the process 300.

As also shown in FIG. 7, an application status or progress menu 712 canbe presented by the process 300 on the screen 700. A defined applicationnumber or identification 720 that is associated with the transfer isshown in the status menu 712. A similar progress bar 716 is displayed inthe status menu 712 to graphically represent the progress being madethrough process 300. A list of steps or items required for completioncan also be shown in the status menu 712, and if a user wants to returnto a previous screen, the user may select one of the steps or itemsdisplayed in the status menu 712. In other words, each step or item maybe presented as a selectable link which allows the user to select acertain step and the web-based program can advance the process 300forward or backwards (via one or more steps) through the process 300. Inaddition, the status menu 712 can further display a selectable button718 which allows the user to save the current transaction at any step inthe process 300. The user can then quit and return later to complete thetransaction by selecting the button 718.

In block 304, the user may be asked for additional information relatedto the transfer and timeshare property. As shown in another screen 800in FIG. 8, the user can select either a “Deeded Week” or “Points” aspart of the transfer. In some cases, the resort property may be neithera “deed” property or a “week” property, and therefore a response may notbe necessary. A text box 802 can be displayed on the screen 800 so thatthe user can manually enter the number of points associated with thetransfer. Alternatively, the process 300 can retrieve from a memoryunit, the server or database and preload the number of points associatedwith the selected property that is available for the transfer. In theevent only a portion of the total number of points is being transferred,the user may be able to adjust the number of points displayed in thetext box 802. Alternatively, if the transfer is for a week, the user canmake the requisite selection. Moreover, the user can enter the unitnumber and week number associated with the timeshare transfer in a firsttext box 804 and a second text box or drop-down menu 806. If there is anadditional unit or week, the user can select a corresponding icon to addthe additional information.

Once the user enters the information requested, a confirmation screencan display seeking confirmation regarding the selections made by theuser. The user can select either to confirm or cancel the informationpreviously entered. To continue to the next screen, the user can selectthe “Next” button 710, or to return to the previous screen the user canselect a “Previous” button 808 on the screen.

In some aspects, on at least one of the screens in this process 300, thescreen can display a plurality of options that are selectable by theuser. For instance, in FIG. 8, the screen 800 displays near the topthereof a first selectable link 810, a second selectable link 812, and athird selectable link 814. The first selectable link 810 can beassociated with a user's profile. The user can select this link 810 andbe directed to another screen that displays profile information for theuser. In this instance, a signal or request can be sent to the server toretrieve information from a user's profile which is saved on the serveror database. This may include the user's name, contact information,property owned as a timeshare or otherwise, completed transactions,pending transactions, transactions in process, etc. The second link 812can offer the user an opportunity to change the password associated withthe user (i.e., user name, login name, email address, etc.). Byselecting the second link 812, the processor can execute a set ofinstructions for displaying a change of password screen (not shown) sothat the user can change the user password. The set of instructions mayform part of the web-based program or may be a separate programexecutably stored on the server. Moreover, the third selectable link 814is a logout link that, by selecting, the processor can execute a logoutscript or process for exiting the transfer process 300. In someinstances, the progress made in a current transaction can be saved sothat the user may return to the same transaction at a later time.

Block 304 of the web-based program can be a data gathering or aninformation collecting step. As shown in the different screen images,the program can execute a set of instructions to retrieve the data orinformation via one or more screens. Once the system has collectedinformation related to the transaction and transfer property in block304, the process 300 can advance to block 306 and execute the set ofinstructions by requesting information about the seller or owner of thetimeshare property. An example of this is shown in a display screen 900in FIG. 9. Information requested can include a full name, maritalstatus, home phone number, mobile phone number, work phone number,country, and complete residential address including city, state, and zipcode of the owner or seller. The screen 900 can display a plurality oftext boxes, menus, and the like to receive this information from theuser.

As residential address information is received by the web-based programin block 308, the server 180 can collect the information in real-timeand search over the network 190 (e.g., the Internet) to verify that theaddress information corresponds to a verifiable address in accordancewith United States Postal Service records. In this disclosure, thisverification can form part of an address verification module. An addressverification box 902 is displayed on the screen 900 and communicateswhether the address is verified in accordance with the United StatesPostal Service records. Once the address, or a similar address, isuncovered, the web-based program can display the residential address onthe screen for the user to review and affirm. Once the address isaffirmed, the user can select a link or button 904 to add another owner,advance to the next screen (via button 710) or return to a previousscreen (via button 808). The system can be setup to auto-fill certaininformation related to a second owner, such as if the first and secondowners share the same residential address information. This informationcan be obtained from the server or database depending on the setup.

In FIG. 9, the screen 900 can be arranged with a selectable menu or link906 to remove a current owner from the property during the propertytransfer. In addition, as the user progresses through the transferprocess 300, the status menu 712 continues to advance through the stepsor blocks to be completed. As shown in FIG. 9, the “Current OwnerInformation” icon or link can be highlighted or displayed in such a waythat distinguishes it from the other steps or icons. In this manner, thescreen 900 alerts the user to which step or steps the user is completingor has completed. Moreover, the graphical progress bar 716 can furtherdisplay that the user is a certain percentage 910 through the process300. In this manner, the user can elect to save the current transactionand return at a later date if necessary.

In block 310, the web-based program or process 300 executes another setof instructions to request the user to select how title in the transferproperty is to be held. In FIG. 10, for example, a screen 1000 candisplay a plurality of selectable icons or buttons 1002 related to titleownership. Here, the screen 1000 displays a first option related tojoint tenant ownership and a second option related to tenants in commonownership. There may be other options in other embodiments, and in someinstances, the options may vary based on the state in which the propertyis located and what is deemed appropriate and legally enforceable underfederal and state laws.

The screen 1000 further displays a statement that the user asserts underthe penalty of perjury that the transfer is being made based on sometype of consideration. A plurality of selectable options 1004 can bedisplayed on the screen 1000 which can be used to indicate a purchaseprice, other value other than a dollar amount, or that no considerationis being paid (e.g., a gift for charity). Other options may be displayedin other embodiments. Once again, to advance from the screen 1000, theuser can click either the “Next” or “Previous” buttons on the screen tomove to a different screen.

As also shown in FIG. 10, the process 300 may offer a display window1006 that allows a user to seek help via a live chat window. The livechat function may be controlled by a separate program or process that isindependent from the transfer process 300. This may be controlled overthe network 190 via a separate, third party web-based program. In anyevent, the screen 1000 can display a link or selectable icon or buttonto access the live chat function. By selecting this link, a differentwindow or program may open on the user's computer to facilitate the livechat function. The type of support is not restrictive and can relate tothe type of transaction, resort type, etc.

In block 312, the process 300 advances to a documentation module or step1102 in which a different screen 1100 can provide instructions and amechanism for the user to upload or transmit additional documentationover the network 190 to the server for processing. An example of thisscreen 1100 is shown in FIG. 11. Here, the web-based program can provideone or more options for how a document or file will be transferred viadrop-down menu 1106. The user can electronically upload an executedpower of attorney document, purchase and sales agreement, or any othertype of document to the network 190 by selecting a selectable icon orbutton 1104 to add a file. The web-based program may be able to receivedifferent file types such as .doc, .docx, .pdf, .jpg, .jpeg, .bmp, .gif,.tif, .png, etc. Other document types may also be receivable via theselectable link or button 1104. Once an instruction is communicated tothe web-based program via button 1106, the user may transferdocumentation via uploading it to the server, electronic mail (email),facsimile, through regular postal mail or other transfer means.

In an alternative aspect of this embodiment, a unique email address canbe created for each user or application based on a unique applicationidentification number. This is further addressed with respect to FIG. 15below. In any event, an email address associated with the applicationidentification number can either be provided by the web-based program, ascript executed by the server, or a third party website or program. Assuch, a document or file may be electronically transferred to the emailaddress associated with the application identification number and alsostored in the database associated with said number. The user can begiven the unique email address for accessing different documents fromthe web-based program.

When uploading information or documentation to the server, the servercan alert the user to a successful upload when a file is electronicallysubmitted. Moreover, if the user desires to send a file via regularmail, for example, the server can pull the address information anddisplay such on the screen for the user. Additional informationincluding order number can also be presented by the web-based program orserver to the user as well.

The process 300 can advance to block 314 to execute a payment block ormodule. Here, the web-based program can request payment arrangementinformation from the user. For example, a new screen 1200 is displayedthat is similar to the aforementioned screens with the status menu 712configured on one side thereof. The screen can display a plurality ofselectable buttons 1202 that present questions to the user for selectingwho will pay transfer fees (e.g., seller, buyer, split, etc.), currentand previous year maintenance fees (if applicable), club dues (if any orapplicable), and previous club dues (if any or applicable). Otherclosing costs can be presented in the screen 1200 as well for the userto select how payment will be handled. Depending on the resort ordeveloper, the type and number of payment options may vary. In anyevent, the web-based program can execute the payment block or module 314to receive the necessary information regarding payment.

In addition to payment information, block 314 can present a plurality oftext boxes 1204 that can be editable by the user to enter informationsuch as broker company name, broker contact name, contact phone number,email address for documents, and residential address informationincluding city, state and zip code. The user may also be asked to verifythat information being submitted is truthful and correct. The user maybe required to click on a box 1206 confirming that such information istruthful and correct.

In block 314, the process 300 can summarize the information entered bythe user and present it in a format similar to that shown in a ReviewApplication & Payment Options screen 1300 in FIG. 13. As shown, theprocess 300 executes block 314 by displaying information includingtimeshare information (e.g., resort name, owner/seller number, type oftransfer, etc.), current owner name(s), new title owner name(s), newtitle information (i.e., purchase price, how title is to be held),broker information, and the like. The screen layout 1300 of FIG. 13 isnot intended to be limiting, and other embodiments may show more or lessinformation depending on what is requested by the process 300 andprovided by the user.

In FIG. 13, the process 300 can further be scripted to display a paymentinformation screen 1302. Information related to the payment of thepurchase price, title transfer fee, and/or closing costs may bedisplayed. The screen can include a drop-down menu 1304 to present theuser with one or more methods of payment. The web-based program orprocess 300 can provide additional instructions to the user to enter thenecessary information (e.g., credit card type, credit card number, nameon credit card, expiration date, security code, zip code, etc.) tocomplete a payment transaction. Once this information is entered by theuser and received by the server, the process 300 may further instructthe user to click an acknowledgment button (not shown) confirming theaccuracy of the information submitted and further acknowledge thepossibility of having to pay an additional charge if revisions oramendments are later required. Once all information is entered, the usercan be provided a “Submit” button (not shown) on the display 1300 toeffectively submit or transfer the application form to the server. Athird party that handles and manages the transfer can be alerted by theweb-based program or an alert from the server to access the submittedapplication form from the server. At this point, the applicationsubmission portion of process 300 is complete and the process canadvance to an evaluation block in Nock 316.

In block 316, the web-based program, server, processor, or othermechanism can evaluate the information received from block 316 anddetermine whether a payment is received and accepted. If, for example, acredit card payment is declined, the process 300 can return to block 314and request the user to resubmit new payment information. If the paymentis accepted in block 316, the process 300 can generate an order numberand submit a receipt electronically to the user's email address in block318. An example of a screen displaying this information is shown in FIG.14.

Additional instructions can be displayed on the screen 1400 in a displayarea 1402. The user can be provided with an opportunity to print thepage or close the window in a second display area 1404. Moreover, theremaining steps or processes required to complete the transfer aredisplayed for the user. Once the application has been submitted by theuser, the application file can be transferred and saved to the server180. An XML file or the like can be created for additional use. The filecan be categorized and saved with other files on the server 180, or itcan be saved to an alternative memory device or location. For example,there may be another server disposed in electrical communication withthe main server 180 via the network 190, such that the main server 180can store the file to the second server and retrieve it as necessary.

In block 320, once the application has been submitted and a receipt iselectronically submitted to the designated email address, the process300 can further instruct the server 180 to select a template for theparticular transfer from a library of templates. The library oftemplates, e.g., a plurality of templates for different uses, can beelectronically stored on the server or in a database on the server. Theselected template can include a plurality of inputs that can receiveinformation from the server (e.g., from the XML file) and merge or linkthe plurality of inputs into the selected template for generating finalclosing documents in block 322. The template and data can beelectrically submitted to SAASPose to merge the information.Alternatively, other mail-merged electronic programs can be used toachieve similar results.

After this, the process 300 can advance to block 324 to prepare andfinalize the final closing documents. The server can electronicallysubmit the final closing documents to the buyer and seller for review.The buyer or seller may need to carry out further steps, and the closingdocuments may provide these instructions. The closing documents can beelectronically generated by the server 180 via a program or other logic.Once documents are reviewed and returned by the buyer or seller, theprocess 300 can import the XML file into its production software inblock 326 and download a word document version of the closing package.This package can be retained in the production software.

In FIG. 15 and as previously described, the web-based program candisplay a screen 1500 as part of the process 300 such that the user cansave a partially completed application at any time. Each screen layoutincluding screen 1500 in FIG. 15 can include the “Save & Quit”selectable button 718 that is displayed in the status menu box 712 andcan be enabled at any time by the user clicking on or selecting it. Whena user does select this button 718, the server 180 can provide anapplication identification number 714 in both the status menu 712 and afirst display window 1502. For instance, the web-based program mayinclude instructions for generating an application identificationnumber, or the server can execute a script for generating a uniqueidentification number for each application. Alternatively, a third partywebsite may be used to create an application number for each applicationstarted through process 300. The user may also create an account at thistime by selecting an appropriate icon being displayed in a seconddisplay window 1504.

In another embodiment, a user may be presented with an option to open apartially completed application or view a pending application (e.g., tocheck for a status update). To do so, the user may need to login orenter into the web-based program similar to that shown in FIG. 4.Alternatively, the user can access his or her profile by selecting theprofile selectable link or button 810 as shown in FIG. 8. Once the userenters his or her information, the server can retrieve all data orinformation related to the particular user. As shown in FIG. 16, theweb-based program can receive the data or information from the serverand display a profile page or screen 1600. The profile data orinformation can be saved to the server, a memory, a database, or otherstorage location such that the server 180, upon request, can locate andsend this information to the processor or web-based program for display.As shown in FIG. 16, the application identification number, resort name,units/points, status, and options can be provided for each applicationsubmitted or started by a user. In other embodiments, the profile pagemay display more or less information. The profile page can be a templatestored in the web-based program and configured to receive and displayinformation that is transmitted to it by the server, for example. Theuser can select one of the applications to either review its contents orcomplete it by selecting an appropriate link or button in a MyApplication box 1602. This option can be available to a user at any timeonce an application has been started.

Similar to completing a partially started application, a user may alsocheck the status of a completed application. For example, a user canlogin into the web-based program in a manner as similarly describedabove. Once logged in, the user may select the profile link or button810 to access his or her profile. Once the server is instructed to pullor retrieve data or information for the user, the server communicatesthese details to the web-based program and the one or more applicationscan be displayed in a screen similar to that of FIG. 16. The user canthen select one of the applications, or if only one application isfound, then the user can select that application similar to thatdescribed above.

Once the user selects an application to review, the web-based programcan merge or position the input data or information received from theserver in a template form similar to that shown in FIG. 17. In otherwords, when the user desires to open a completed application, a commandis sent to the server 180 to retrieve the file (i.e., data orinformation) associated with the submitted application. The server 180then communicates the contents of the file to the web-based program andthe contents of the file can be displayed in a manner similar to thatshown in the screen 1700 of FIG. 17. The contents of the file can bedisplayed in an arrangement that identifies the application order numberor file number 1702, one or more steps in the process that have beencompleted, one or more steps not yet completed, and a current step inthe application process 300.

In FIG. 17, the web-based program can arrange the steps or blocks of theprocess 300 in the three aforementioned categories. Other categories maybe displayed as well. In doing so, each category of steps or blocks canbe identified in a specific way, e.g., with a different color, font,print, etc. In FIG. 17, for example, a first category 1704 of steps orblocks is shown or highlighted in a first color. Here, the firstcategory 1704 corresponds to those steps or blocks in which informationrequested via the process 300 have been received as inputs from theuser. This first category may be color-coded green or highlighted with agreen color indicating these steps or blocks have been completed.

In a second category 1706, a current step or block in the process 300 isidentified in a different way. Here, the current step or block can beidentified with a blue color or highlighted in such a way to signifywhere in the process information was last received or the next step inthe process to be completed. The second category 1706 can clearlyidentify this as the current step or block in the process 300, and alsoidentify an anticipated or estimated date of completion and provide adate. This is shown as an example in FIG. 17.

In a third category 1708, one or more blocks or steps that have not yetbeen completed in the process 300 are identified. These blocks or stepscan be identified by a different color, font, shape, size, etc. from thefirst and second categories. In addition, each uncompleted block or stepcan identify the action and estimated date of completion. In thismanner, the web-based program can provide an estimated date forcompleting the transfer process.

In other aspects, a closing date (if known), buyer and seller names,closing officer, settlement agent, description of ordered items, and alist of documents related to the transfer may also be provided in asimilar application status window or screen. Moreover, it is to beunderstood that the server can display more or less informationdepending on the type of template stored in the web-based program. Theweb-based program can be constructed to include a library of templates,and depending on the template, all or only some information may bedisplayed.

In a further aspect, the web-based program may provide the user with anability to open any of the documents in the application status window orscreen by clicking on said document in a display window (not shown), asthe document can include a link or button that communicates a command tothe processor or server 180 to display the requested information. Thisinformation can be saved to a main database, server, memory, etc.Moreover, the user can print the status page or any of the documentsshown in the display window. As the information is displayed in the fileinformation display box or window, each document can include a timestamp or history function that shows when a file was submitted,reviewed, or last manipulated. The time stamp or history can include adate and time, although in other embodiments this can be displayeddifferently. In addition, the size of each file can be displayed. In theevent certain items or documents require ordering, this can be displayedin the file information display box or window.

Other aspects of the method 300, and in particular to the overall systemsetup and arrangement, are only provided as examples. The screen layoutsand information contained therein are only provided as examples of howthe system can operate and are not intended to be restrictive. Moreover,one example of the method and web-based program is available athttp://home.timeshareproplus.com, which is hereby incorporated byreference. Timeshare Pro Plus includes a plurality of modules and is acloud-based Software-as-a-Service (SAAS) application that performsvarious functions such as those described in this disclosure.

As described above, the aforementioned process 300 can be adapted for anowner-to-owner transaction or a transaction involving a broker titlecompany. In the event a broker title company is involved in thetransaction, the broker title company may be required to register anaccount in its name. An example of this is shown in a different process1800 shown in FIG. 18. The process 1800 can include a plurality ofblocks for executing a timeshare transfer. The process 1800 may includeone or more blocks similar to that of the previously described process300. For instance, the process 1800 can include a first block 1802 thatis executed by a web-based program. Alternatively, the process 1800 canbe stored on a memory device or computing device and thereby executed bya processor. In a web-based program, the user may open the web-basedprogram by accessing it through the Internet and opening a web browser.In the first block 1802, the user may be required to create a newaccount or open an existing account. If the user is a broker titlecompany, the web-based program may first display a screen similar tothat of FIG. 4. If the broker title company already has an existingaccount, the user can enter an email address and password thatcorresponds with the existing account. In doing so, according to block1804 of the process 1800, the email address and password arecommunicated by the web-based program to the server, and the server cansearch a database of existing accounts to determine if the informationsubmitted corresponds to an existing account. If an existing accountfile is located, the server can communicate this to the web-basedprogram. As such, the web-based program (i.e., web-based program) canadvance the process 1800 to block 1804.

If, however, an existing account is not found or the user selects tocreate a new account, a different module or script corresponding toblock 1804 can be executed by the web-based program. Here, the web-basedprogram can collect different information including at least an emailaddress and password to create an account. The web-based program mayrequest additional information, including the name of the broker titlecompany, address information, correspondence information, and a securityquestion or two in case the user later forgets the password for theaccount. In any event, once new account information is submitted by theuser, the web-based program sends this information over the network tothe server, and the server can create a new account file and store thedetails thereof in the database of existing accounts. The server maysave this file in a different location as well. This is one example ofthis embodiment.

Upon completing the requirements for logging into the system, theprocess 1800 can advance to a start application module within theweb-based program in block 1806. As the start new application module isexecuted, the process 1800 can advance to block 1808 where the user ispresented with a screen similar to that of FIG. 6. Here, the web-basedprogram requests the user to identify itself as an owner, broker titlecompany, transfer company, or other party. This can be executed byproviding a drop down menu 602 as shown in the screen 600. Moreover, theweb-based program can provide the user with a list of requirementsnecessary for executing the process 1800. The user may be asked to checka box or otherwise affirm the requirements. Alternatively, the user mayaffirm the requirements once the start application button or link 610 isselected. The web-based program may further request information aboutthe developer of the property in block 1808. This information may becollected from the user in drop down menu or text box 608. Once the userhas entered the information requested from the web-based program andselected the start application button 610, the web-based program cancommunicate this information to the server. The server can receive thisinformation and begin producing an application file that correspondswith the email address and password of the user.

Once block 808 has been completed, the process 1800 can advance to block1810 to execute a resort property information collection module. Theweb-based program can execute this block by using a screen similar tothat of FIG. 7 or FIG. 19. In particular, the web-based program canexecute the module to request information from the user including resortname, who the transfer is being made to (e.g., new owner, company, trustaccount, add new individual to title, remove someone from title due todeath, marital status change, or for another reason, etc.), owner number(if applicable), and if a power of attorney is being used by either thebuyer or seller.

In FIG. 19, for example, a screen 1900 can be displayed to the user bythe web-based program. Here, the user can be identified as a brokertitle company, owner, or some other party via menu 1902. The manner inwhich the transfer is being made can be selected according to one of aplurality of options 1904 identified in the screen 1900. Moreover, theuser can select the developer in menu or text box 1906 and the homeresort in menu or text box 1908. The user can enter his or her ownernumber in text box 1910 and further identify the use of a power ofattorney document in one of the plurality of options 1912 on screen1900. As the user submits the information, the web-based program maycollect and transfer the information to the server or the information istransferred directly to the server. The server can take the informationand save it in a file in the database. Alternatively, the web-basedprogram can save the information until the process 1800 is complete.

Once the module 1810 is complete, the user can select the “Next” button1914 on the screen and the process 1800 can advance to block 1812 toexecute a title type module. The title type module can be saved on theserver or database and presented to the user by the web-based program ina screen display similar to that of FIG. 8 and FIG. 20. In FIG. 20, forexample, the web-based program can display a screen 2000 for collectinginformation related to the type of title being transferred. Forinstance, the web-based program can request information such as transferoptions in a first menu 2002 and title insurance options in a secondmenu 2004. As the user selects an option from each menu, the web-basedprogram can execute a fee calculation module stored on the server ordatabase to determine an estimated fee for the transaction. The feecalculation module can take into account the developer type, resorttype, resort location, insurance costs, type of transfer being made, andwhat type of documents may be required to execute the transaction. Asinputs to the fee calculation module are received by the web-basedprogram, the web-based program can execute the calculation module anddisplay the estimated fee in the box 2006 on the screen 2000.

In FIG. 20, the user may also be requested to provide the web-basedprogram with a unit number 2008 and week number 2010 associated with thetransfer property. In some instances, the unit and week numbers may beused as factors in the fee calculation module. Moreover, if more thanone unit or week is involved in the transaction, the user can enteradditional information in the selection area 2012 of the screen 2000.Additional units or weeks can also be inputs to the fee calculationmodule, and as additional information is provided to the module, theestimated fee can be automatically and continuously updated asnecessary. Upon completion of the inputs in the title type module, theuser can select the “PREVIOUS” button 2014 to return to block 1810 orthe “NEXT” button 2016 to advance the process 1800.

Once block 1812 is complete, the process 1800 advances to block 1814 tocomplete an owner information module stored on the server. In thismodule, the web-based program can receive information about the owner ofthe property. A screen similar to that in FIG. 9 can be used to collectthis information. In particular, the web-based program can collectinformation such as whether the owner is an individual or company, theowner's name, marital status, country of residence, address, home phonenumber, work phone number, mobile phone number, email address, and anyother information necessary to complete the transaction. Similar to thatin FIG. 9, the block 1814 can receive the owner's address informationand perform an address validation module to determine whether theaddress is valid. To do so, the web-based program or server can collectthe address information from the user and submit the information overthe network to the United States Postal Service or a third partyverifier. Once the Postal Service or third party verifies the address asbeing valid, the server can alert the user via the web-based program tothe verification of the address.

In addition, the owner information module can allow the user to removean owner during the transfer or add another current owner. Examples ofthis are shown in FIG. 9. Once the user submits the informationrequested in the owner information module, the web-based program cansave the information to the server to be saved in a file on the serveror in the database. The owner information module in block 1814 can alsocollect information about the new owner. An example of this is shown ina screen 2100 in FIG. 21. The screen 2100 can include several menus ortext blocks for the user to enter information therein. For instance, ina first menu or text block 2102, the user can be requested to enter thefull name of the new owner and the marital status. In a second menu ortext block 2104, the user can submit the email address, home phonenumber, and work phone number of the new owner. In a third menu or textblock 2106, the address information for the new owner can be provided.Upon entering the address information for the new owner, the addressverification module stored on the server can be executed by theweb-based program in a manner similar to that previously described. If asecond or additional new owner needs to be added, a link 2110 can beselected such that a new owner can be added similar to that in FIG. 21.The new owner information can be saved in a file on the server or in thedatabase, for example.

Upon completion of the owner information module in block 1814, theprocess can advance to the new title module stored on the server inblock 1816. The new title module can be executed by the web-basedprogram in a manner similar to that described above and shown in FIG.10. Alternatively, a new display 2200 as shown in FIG. 22 can beprovided by the web-based program to request information from the user.As shown, the user can be provided with a plurality of options 2202 forhow the property will be vested, e.g., joint tenants or tenants incommon. The user can also be presented with a plurality of statementsthat the user agrees with by selecting the “NEXT” button 2206 fromscreen 2200. The user may be required to acknowledge whether thetransfer is a gift to a family member, a transfer where no considerationis paid, a transfer to a family member for a purchase price, or atransfer to a non-related person or entity for a purchase price. In someinstances, the user may be required to enter a purchase price.

Once the new title module in block 1816 is completed, the process canadvance to block 1818 where the web-based program executes adocumentation module. The documentation module can be a separate modulefrom the other modules and stored on the server or database. An exampleof the documentation module is shown in FIG. 11 and described above. Inparticular, the user may be able to submit a power of attorney document,a purchase and sales contract, or any other documentation required bythe web-based program to complete the closing documents for thetransfer. The user may elect from screen 1100 whether the documents willbe uploaded and transferred electronically, submitted via facsimile, orsubmitted via mail. Other means for submitting the documents arecontemplated by this disclosure, and thus the disclosure should not belimited to these examples. Information may be provided by the web-basedprogram to the user for how to fax or mail copies of the documents inthis block 1818.

Once the documentation module has been executed in block 1818, theprocess can advance to block 1820 and the web-based program can executea notification settings module, which can be stored on the server or inthe database. In the notification settings module, the web-based programcan gather information such as how transfer fees will be paid, howcurrent and prior year maintenance fees will be paid, and how currentand prior year club dues will be paid. The web-based program can alsocollect information related to the broker company name (if applicable),the broker contact name, phone number, email address, and physicaladdress. An example of a screen display is shown in FIG. 12 anddescribed above. Once the web-based program receives the informationfrom the notification settings module, the web-based program cancommunicate this information to the server and this information can besaved to the server. In some aspects, the information collected in block1820 can be used by the fee calculation module to further determine anestimated fee for the transfer.

Once the notification settings module in block 1820 is completed, theprocess can advance to block 1822 and the web-based program can executea review application and payment module stored on the server. An exampleof this is shown in the display screen 1300 of FIG. 13 and describedabove. In this module, the web-based program can coordinate with theserver and compile the information collected in the previous modules.Once compiled, the web-based program can structure the information in aformat similar to that shown in FIG. 13. In this way, the user caneasily review the information previously submitted, and if an error ispresent, the user can use the status window 712 to return to a previousscreen and correct any error. If the information is correct, the usercan submit payment to complete the transaction. This is shown in FIG. 13in a payment window 1302. The fee payment module has calculated theestimated title transfer fee based on the information collected inprevious modules and the fee can be displayed to the user. The user canthen select a method of payment 1304 and complete the payment. A thirdparty can control the payment process and collect the necessary fees tocomplete the title transfer process 1800. Additional modules can bestored on the server and executed by the web-based program such as thoseshown in FIGS. 14-17.

Once block 1822 is executed, the process is completed. Nevertheless, theweb-based program can present the user with a plurality of options suchas those shown in FIG. 23. For example, the web-based program canexecute another process whereby the applicant is presented with anoption to start a new application, finish an existing application, orcheck a status of a previously submitted application. In FIG. 23, theweb-based program can execute this process by displaying a first screen2300 to the user. Instructions can be sent from the server to theweb-based program and to the user's computer over the network, and inthis screen the web-based program provides the plurality of options tothe user. To begin a new application, the web-based program can displaya first selectable link or button 2302. To finish an existingapplication, the web-based program can display a second selectable linkor button 2304. To check the status of a previously submittedapplication, the web-based program can display a third selectable linkor button 2306.

If the first selectable link or button 2302 is triggered, a signal canbe sent to the web-based program over the network and the web-basedprogram can interpret the signal and send instructions over the networkto the user's computer to execute a process similar to that of FIGS. 3and 18. If, however, the second selectable link or button 2304 istriggered, a signal can be sent to the web-based program over thenetwork. Upon receiving the signal, the web-based program can sendinstructions to the server to retrieve a file corresponding to anunfinished, existing application. This application may be stored on theserver or in a database as previously described, and the file can besaved in such a manner that it is identifiable with a login and passwordpreviously submitted by a user to the web-based program. Thus, theweb-based program can send instructions to the server to retrieve thefile and also provide the user's login (e.g., email address) andpassword so that the correct file can be retrieved from the database. Inthe event there is more than one existing file that corresponds with thelogin and password, both files can be transferred to the web-basedprogram. The web-based program can therefore receive both files and sendinstructions over the network to the user's computer to provide the userwith an option to select between the two or more files. Once the desiredfile is selected, the web-based program can return the unselected fileto the server.

Similarly, if the third selectable link or button 2306 is triggered, theweb-based program can send a request to the server to retrieve allcompleted applications from the database that correspond with the loginand password. The server can pull these files from the database, andsend all files to the web-based program. Alternatively, if a user hasnot logged into the web-based program, the web-based program can displaya screen 2400 similar to that of FIG. 24. Here, the user can be asked toidentify the completed applications based upon the owner's last name andorder number 2402 or email address and password 2404. There may be otherways to identify the applications and those shown in FIG. 24 are onlyone example. The web-based program can execute the aforementionedprocess, and if the user supplies information based on 2402 or 2404, theweb-based program can send this information to the server to locatefiles associated with the submitted information. In the event no filecan be found, the server can provide this information to the web-basedprogram and the web-based program can further execute the process byasking if the user wants to start a new application. As such, the useror applicant can retrieve a previously existing application since eachapplication is assigned its unique identification code or number. If theapplicant is unable to produce the identification code or number, theapplicant may submit a previously established email address and passwordto achieve further assistance. In the event the information is found onthe server or in the database, the server can communicate thisinformation to the web-based program such that the information can bepresented to the user in a format similar to that in FIG. 17.

Another aspect to the present disclosure is the generation of closingdocuments required for the transfer and closing of a timesharetransaction. The documents may be stored on a server, in a memory unitof a computing system, or in a database, such that once information issubmitted in an application (as described above), the necessarydocuments can be prepared and submitted to the party or parties of thetransaction for review and execution. In other words, once anapplication is completed via a process similar to application process300 or application process 1800, the web-based program can execute ascript, logic, or set of instructions stored on the server for producingthe necessary forms or documents as another step for closing thetimeshare transfer.

In FIG. 25, one example of a set of executable instructions is providedfor producing the documents and forms. It is to be understood that theweb-based program is operable in conjunction with the server forexecuting the set of instructions. In particular, one transaction may bedifferent from another based on the parties involved, such as, forexample, whether a title broker company is involved, the type ofdeveloper, resort property, resort property location, the laws of eachindividual state or country where the developer and/or resort islocated, the number of parties involved in a transaction, and the feesinvolved in the transaction. In other words, the set of instructions inFIG. 25 may not be executed for each transaction, and the web-basedprogram can be executed in such a way that based on information receivedfrom the user the program or server can determine which documents arerequired for a certain transaction, thereby allowing the web-basedprogram to produce the required documents and forms for execution.Examples of different documents and forms that can be produced in theset of instructions 2500 of FIG. 25 are shown in FIGS. 26-42.

The set of instructions 2500 can be a script, program, method, module,logic, or process executable by the web-based program and/or a processorof a computer to produce the documents and forms for carrying out thetransfer. For simplicity, the set of instructions 2500 will be referredto as the forms process 2500. In a first block 2502 of the forms process2500, a determination is made by the web-based program or server whetherthe application is complete. Here, the previously described processes300, 1800 or variants thereof may have been executed and the user hassupplied requested information. Once the application process, i.e.,process 300 or 1800 or some variant thereof; is completed, the formsprocess 2500 advances to block 2504 and each of the inputs received bythe web-based program from the user are assigned unique, predefinedidentifiers or variables. In the event the application process is notcomplete, block 2502 is repeated until the process is complete.

In the to-be-generated documents and forms, in many instancesinformation can be pulled directly from the application and transferredto the appropriate location on these documents. As will be describedbelow, one or more of these documents or forms can be stored as atemplate on the server or database and merged with correspondingidentifiers that link information being input into the application(e.g., seller name, address, etc.). Seller's name can be identified orlinked by a variable “$ {sellerName1}”. If there are two sellers, then asecond variable can be “${sellerName2}”. The resort name can beidentified by variable ${resortName}. Again, the aforementionedalgorithms can be structured such that an applicant can enter the firstseller name into a corresponding location in the application, and thevariable ${sellerName1} is assigned or linked to the input entered intothat location in the application. Moreover, this and each variable (oridentifier) can be saved in the memory unit of the computing device, onthe server, or in a file in a database so that other documents where thesame variable is required, the content of that variable can be retrievedfrom the server and inserted into a document at the assigned location.

In block 2504, unique identifiers or variables are assigned to aplurality of the inputs. The plurality of inputs can include the buyer'sname, buyer's address, buyer's phone number, seller's name, seller'saddress, seller's phone number, file number, date of submission, feesdue, title broker company name, etc. The processes 300, 1800 previouslydescribed can be developed such that as the user enters buyer'sinformation in blocks 2102, 2104, and 2106 of FIG. 21, for example, theweb-based program can correlate and merge this input data with one ormore of the identifiers. The inputs and identifiers can be linked andmerged into a file on the server, and the server can store the file withthe inputs and identifiers either on the server or in the database.

Once the inputs are assigned to the identifiers, the forms process 2500can advance to any of blocks 2506 through 2536. Based on how the inputsare linked with the unique identifiers, the web-based program or server(e.g., via a determination module stored on the server) can make adetermination which documents or forms are required to complete adesired transaction. The document generation portion of the formsprocess 2500 can be executed in blocks 2506 through 2536. In addition,the documents or forms shown in FIGS. 26-42 are only examples. Certaindevelopers or resorts may require different or additional documents forexecution. In any event, the documents and forms can be stored in atemplate library on the server or in a database. As such, the necessarydocuments and forms can be obtained and prepared within a short amountof time after the application is submitted and all inputs have beenreceived.

In block 2506, for example, the forms process 2500 can execute andgenerate a welcome and instruction letter for the buyer and seller basedon a letter template 2600. In one example, a welcome or introductionletter can inform the party or parties that the transaction order hasbeen received and the process has been initiated. Fees may betransferred to an escrow account, bank account, or other location duringthe process. The welcome letter can inform the party or parties aboutthe timing of such a transaction and what expectations of the differentparties may be. Contact information may be provided for any questionsduring the process. An example of the letter template 2600 is shown inFIG. 26. The letter template 2600 can include an identifier “$ {eDate}2602 which corresponds to a predetermined date set forth from the dateall inputs are received by the web-based program. For instance, the dateidentifier 2602 may correspond to the date all inputs are received bythe web-based program, or it may refer to some other date based off thedate all inputs are received. In any event, the date identifier 2602 canbe predefined within the forms process 2500 such that the date can beinput into the letter template 2600 in the position shown.

The forms process 2500 can advance to block 2508 and generate a filecover page. Here, a file cover page template can be stored on the serveror database, or the web-based program can process the informationprovided in the application and merge information from the applicationinto predefined fields in the file cover page template. As such, a filecover page module can be executed by requesting the file cover pagetemplate from a template library (e.g., stored on the server), and theidentifiers in the file cover page template can be merged with theinputs received from the user.

In FIG. 27, an example of a file cover page template 2700 is shown.Here, the file cover page template 2700 can include a plurality ofidentifiers that correspond to the buyer, seller, resort, and feestructure. In one example, identifier ${fileNumber} 2702 corresponds toan assigned file number or application number for a given transaction.The file or application number can be assigned by the web-based programin an incremental or random fashion. Other identifiers can includeseller name, seller address, seller phone number, seller email address,buyer name, buyer address, buyer phone number, buyer email address,resort name, unit number(s), unit week(s), purchase price, brokertransfer fee, current year maintenance fee(s), current year club fee(s),past year(s) maintenance fee(s), and past year(s) club fee(s). Moreover,other identifiers may include the date identifier 2602, processoridentifier, file review identifier, additional documents requested orreceived, estoppel ordered, and date documents and forms submitted toresort. The file cover page template 2700 is only shown as an example,and one skilled in the art can appreciate that additional identifiersmay be provided on other templates, or in some instances, the templatemay be tailored for a given transaction. In any event, the inputsreceived can be inserted or merged into each location in the template2700.

The forms process 2500 can advance to block 2510 and produce a filechecklist for buyers and sellers. A checklist may be generated andidentify certain or all documents required from each party (e.g., buyerand seller). These listed documents can include a sellers authorization,charitable donation form, donor letter stating fair market valueassigned, third party transaction agreement, purchase and salescontract, compliance agreement, resort transfer form, LLC affidavit,power of attorney (and accompanying information or documents), completedW-9 forms, identification forms or cards of buyer and/or seller. Formsspecific for buyers can include documents necessary in the event abusiness entity is taking title (e.g., articles of incorporation,corporate resolution, certificate of good standing) and other documentssimilar to those for seller.

In FIG. 28, an example of a seller checklist 2800 is shown. In FIG. 29,an example of a buyer checklist 2900 is shown. Each checklist can begenerated in block 2510 and include one or more identifiers thatcorresponds with one or more inputs received from the user. Other itemsmay be provided on different checklists, and FIGS. 28 and 29 are onlyintended to provide an example of what each checklist might include fora given transaction.

In block 2512, the forms process 2500 can generate a third partytransaction agreement. An example of a third party transaction template3000 is shown in FIG. 3. The template 3000 can include the dateidentifier 2602 along with other identifiers (not shown). Like the othertemplates, the third party template 3000 can be stored on the server ordatabase in a template library.

The forms process 2500 can advance to block 2514 to request a complianceand correction agreement template 3100 similar to the one shown in FIG.31. The compliance and correction agreement template 3100 can include aplurality of identifiers as shown, and based on the inputs received, theinputs can be disposed or merged in each location as shown in FIG. 31.For example, the file or application number can be disposed in the filenumber identifier location 2702. Other identifiers can include theseller's name(s) and buyer's name(s).

Upon completion of the compliance and correction agreement template3100, the forms process 2500 can advance to block 2516. In block 2516, aresort transfer form template can be requested from the template libraryand the server can provide a resort transfer form template 3200 similarto the example shown in FIG. 32. The resort transfer form template 3200can include a plurality of identifiers including identifierscorresponding to seller's name(s) (e.g., ${sellerName1}), buyer'sname(s) (e.g., ${buyerName1}), seller's address(es) (e.g.,${sellerAddress}), buyer's address(es) (e.g., ${buyerAddress}), seller'sphone number(s) (e.g., $ {sellerPhone}), buyer's phone number(s) (e.g.,${buyerPhone}), seller's email address(es) (e.g.,${sellerEmailAddress}), buyer's email address(es) (e.g.,${buyerEmailAddress}), resort name (e.g., ${resortName}), unit number(e.g., ${unitNumbers}), and week number (e.g., ${unitWeeks}). Otheridentifiers may include developer name, submission date, etc. Aspreviously described, each of these identifiers corresponds to an inputprovided by the user during an application process similar to that ofprocess 300 and process 1800. As such, each input is linked with acorresponding identifier, and upon requesting the resort transfer formtemplate 3200, a resort transfer form can be produced by linking eachinput with the corresponding identifier in the template.

Upon completing the resort transfer form in block 2516, the formsprocess 2500 can advance to block 2518 to generate an additionalpurchaser form. The additional purchaser form can be part of the resorttransfer form, or it may be a separate document. In any event, in block2518 an additional purchaser form template 3300 similar to the exampleof FIG. 33 can be provided from the server. The template 3300 caninclude a plurality of identifiers that correspond to inputs receivedduring an application process. The additional purchaser form can beproduced by linking each input with the corresponding identifier asshown in FIG. 33. In the event there are no additional purchasers, therewill be no inputs corresponding to any of the identifiers in theadditional purchaser form template 3300. The web-based program or servermay detect this once the application is completed in block 2502, andthus block 2518 may be skipped. Similarly, other blocks in the formsprocess 2500 can be skipped based on the inputs received.

The forms process 2500 can advance to block 2520 to produce a salescontract or contract between the parties. A contract template 3400similar to the example in FIG. 34 can be stored in the database or onthe server and communicated to the web-based program upon an instructionto do so. The contract template 3400 can include a plurality ofidentifiers including the date identifier 2602 and file numberidentifier 2702. Other identifiers similar to the ones described withrespect to FIG. 32 can form part of the template 3400. In addition,identifiers corresponding to a purchase price (e.g., ${salesPrice}),transfer costs (e.g., ${brokerTransferFeePayer}), current yearmaintenance fees if due to be paid by (e.g.,${brokerMaintenanceFeePayer1}), current year club dues if due to be paidby (e.g., ${brokerClubFeePayer1}), previous year maintenance fees if dueto be paid by (e.g., ${brokerMaintenanceFeePayer2}), previous year clubdues if due to be paid by (e.g., ${brokerClubFeePayer2}), joint tenantsto hold title (e.g., ${vestedJoint}), and tenants in common to holdtitle (e.g., ${vestedCommon}). Moreover, while not shown in FIG. 34,other identifiers may include sales commission (if applicable), realestate broker (if applicable), and any other way title may be heldfollowing the transfer. Once the inputs are inserted into the template3400, the sales contract is produced in block 2520.

The forms process 2500 can advance to block 2522 and generate anauthorization to release information to title company document. Here, atemplate 3500 similar to the one shown in FIG. 35 can be stored in theserver or database. The template 3500 may include a plurality ofidentifiers corresponding to inputs received from the applicationprocess. The identifiers can include the date identifier 2602 and filenumber identifier 2702 as previously described. The inputs can be linkedto their respective identifier and the authorization to releaseinformation to the title company document can be produced in block 2522.

The forms process 2500 can also execute the necessary actions to producea Certificate of Trust document in block 2524. The Certificate of Trustdocument can be produced by linking inputs with identifiers in aCertificate of Trust template 3600 similar to the one shown in FIG. 36.Once the inputs are linked with their respective identifiers, theCertificate of Trust document is produced.

In block 2526, an Attorney in Fact Affidavit for Power of Attorneydocument can be produced via the forms process 2500. Here, a template3700 similar to the one shown in FIG. 37 can be stored on the server orin the database, retrieved by the server, and inputs can be linked tocorresponding identifiers in the template 3700. Once the inputs arelinked with their respective identifiers in the template, the Attorneyin Fact Affidavit for Power of Attorney document is produced.

The forms process 2500 can further execute the steps necessary toproduce a Name Affidavit document. A Name Affidavit document can beproduced by executing block 2528 and linking inputs with theirrespective identifiers in a Name Affidavit template 3800 similar to theone shown in FIG. 38. For instance, the template 3800 can include thefile number identifier that is linked with the predetermined file orapplication number. Other identifiers, such as those corresponding withthe seller's name(s), can also be linked in the template 3800.

In FIG. 39, an example of a Limited Liability Company (LLC) Affidavittemplate 3900 is shown. The template 3900 can be stored in the templatelibrary in the database or on the server. The server can send thetemplate 3900 to the web-based program or process and each identifier inthe template 3900 can be linked or merged with its corresponding input.The template 3900 can be completed in block 2530 to produce the LLCAffidavit.

The forms process 2500 can advance to block 2532 to generate aContinuous Marriage Affidavit document. The Continuous MarriageAffidavit document can be produced by linking the appropriate inputswith one or more identifiers in a Continuous Marriage Affidavit template4000 similar to the one shown in FIG. 40.

The forms process 2500 can also execute the conditions set forth inblock 3534 to produce a Fees Due Notice document. The Fees Due Noticedocument can be generated by linking the appropriate inputs with one ormore identifiers in a Fees Due Notice template. An example of a Fees DueNotice template 4100 is shown in FIG. 41. Like the other forms anddocuments shown and described in this disclosure, the Fees Due Noticetemplate 4100 is only one illustrative example of this embodiment, andother templates may be completed to generate similar Fees Due Notices.

The forms process 2500 can further advance to block 2536 where anOwner/Seller Affidavit template 4200 similar to the one shown in FIG. 42can be retrieved by the server. The template 4200 can include aplurality of identifiers that are linked to inputs received by theweb-based program or server. Once the inputs are inserted or linked tothe respective identifier, the Owner/Seller Affidavit is produced inblock 2536.

The forms process 2500 can also produce additional documents other thanthose described herein. In some embodiments, the forms necessary for atransaction can depend on the type and number of parties involved, theunderlying state or federal laws, the type of transaction beingcompleted, the type of property subject to the transaction, thedeveloper or resort that owns the property, etc. Thus, for thisdisclosure, the forms process 2500 disclosed herein is only intended tobe an example of one such process for producing the necessary documentsto be executed by the party or parties of the transaction.

In another aspect of this disclosure, the application process ofcollecting information for a timeshare transfer and producing documentsto complete the transfer can form part of a larger process. An exampleof this is shown in process 4300 of FIG. 43. The process 4300 caninclude a plurality of procedures or steps for completing the overalltransfer process. The process 4300 can include processes 300, 1800, and2500 as will be described. Moreover, the process 4300 can be executed aspart of an algorithm stored on the server or as part of a web-basedprogram similar to the one described above for executing processes 300and 1800. Alternatively, process 4300 can be handled by more than onesource. A computing system may include a memory and processor, asdescribed above, such that the memory stores instructions therein forthe processor to execute one or more of the procedures or steps of theprocess 4300. As another example, a financial institution or bankingsystem may execute one of the steps that relates to payment or feescollected. For purposes of the illustrated embodiments, reference willbe made to a web-based program that executes one or more blocks andmodules stored on the server.

In FIG. 43, the process 4300 can begin with a first block 4302 where theapplication process is completed. An example of this is the process 300shown in FIG. 3 or the process 1800 shown in FIG. 18. In these examples,the parties of the transaction may include one or more individuals, acorporate entity, a broker title company, a charity, or other knownentities. In block 4302, information is collected from a party toinitiate, enable, or trigger a timeshare property transfer transaction.

Once the information is received in block 4302, the process 4300 canadvance to block 4304. Here, a determination is made if all payments andfees have been collected from one or each of the parties of thetransaction. This may be determined by a third party such as a bank orfinancial institution. Alternatively, the transaction file stored on theserver or in the database may track payments received. Other means forcollecting and tracking payments may be included in block 4304.

Process 4300 can advance to block 4306 where the closing documents andforms can be generated and delivered to each party. The documentgeneration process is similar to the forms process 2500 of FIG. 25. Onceall documents and forms have been generated, the aforementionedweb-based program can electronically transfer the documents and forms toeach party. For example, if a seller email address and buyer emailaddress are provided in the application process, the email address foreach party can be used as a means for electronically transferring thedocuments and forms. In another example, documents and forms can bemailed to the address of each party based on information supplied duringthe application process. Other communication means such as facsimile canbe used in block 4306.

Once the documents and forms have been submitted to each party, theprocess 4300 can advance to block 4308 where a determination is madewhether all documents and forms have been received as completed. In someinstances, electronic signatures and the like can be used for executingdocuments, and in these instances the entirety of block 4308 can beexecuted electronically by a computing system or the web-based program.In other instances where original signatures are required, andparticularly notarized signatures, a third party may be used to reviewthe executed documents and forms for completeness and accuracy. In otherwords, block 4308 can be executed automatically, manually, or bothdepending on the document or form being executed. If each document andform is received and a determination is made that each is complete andaccurate, the process 4300 can advance to block 4310. If, however, oneor more documents is not received, complete or accurate, the process4300 may not advance past block 4308 until all documents and forms arereceived and verified as being complete and accurate.

Once block 4308 is completed, the process 4300 can advance to block 4310to order an estoppel and verify account information with the developerof the timeshare property. One example of ordering an estoppel isexplained below with reference to FIG. 44. However, in another examplethe information gathered from the application process of FIG. 3 or FIG.18 can be used to complete an application for holding an estoppel.Moreover, in block 4310, the web-based program or computing system canelectronically transfer the executed documents and forms, along with acopy of the completed application and any other required documents, tothe developer of the timeshare property for verification of the detailsthereof. The same information and documents can be transferred viafacsimile or mail as well.

In block 4312, the process 4300 makes a determination whether theestoppel is ordered and the developer has verified the details of theapplication and closing documents and forms. In one aspect, block 4312can be performed electronically by the web-based program or computingsystem. In other aspects, block 4312 may be performed by a third partyor manually. Once the determination is made in block 4312, the process4300 executes block 4314 and confirms that the owner's account balanceis zero and there are no other fees or payments due (e.g., maintenancefees, club fees, mortgage payments, insurance payments, etc.). Inaddition, the fees or payments required by the developer for thetransaction can be transferred thereto. Any third party fees can also betransferred to the appropriate party. The sales or purchase price of thetransaction can also be confirmed as paid in this block.

The process can advance to block 4316 to send a complete file andexecuted documents to the developer. The complete file may be stored inthe database or on the server, and as such a copy of the file can betransferred to the developer. In some instances, the developer mayinclude a first right of refusal which may impact the execution of block4316. In any event, the final acceptance of the transaction can beconsummated in blocks 4316 and 4318. This may involve recording anydeeds or other documents with the appropriate government authorities.Other tasks may be completed as well in block 4318.

In another embodiment of this disclosure, the aforementioned web portal(program) or web-based program can be used for handling a request for anestoppel application. This is similar to block 4310 in FIG. 43. In oneexample, this can be handled through a similar URL or website as thetimeshare transfer process of FIGS. 3 and 18. Alternatively, anindependently distinct URL or website may be available for completingthe process. One such example may be found athttp://www.RequestMyEstoppel.com.

One example of a process 4400 for requesting an estoppel is shown inFIG. 44. This process 4400 can include one or more steps similar to theprocesses of FIGS. 3 and 18. For instance, once the user accesses theweb portal or web-based program over the network (e.g.,http://www.RequestMyEstoppel.com), the web-based program can execute theprocess 4400 by first advancing to a first block 4402. In the firstblock 4402, the web-based program can execute a welcome screen module.The welcome screen module can be stored on the server and display ascreen 4500 similar to that shown in FIG. 45. In this screen 4500, theuser can be presented with a plurality of options for advancing beyondthe welcome screen 4500. For example, the user can select a first linkor button 4502 to start a new application, a second link or button 4504to finish an existing application, or a third link or button 4506 tocheck a status of a completed application. A fourth link or button 4508allows a user to log into their file, which can be stored on the serveror database. In addition, a fifth link or button 4510 can allow a userto access customer support or otherwise seek help.

Once a link or button is selected from the welcome screen 4500, theprocess 4400 can advance to block 4406. If the user selects the firstlink or button 4502, the web-based program can receive a signalindicative of the selection and advance the process 4500 to block 4404.If, however, the user selects the second link or button 4504, theweb-based program can receive a signal indicative of this selection andadvance the process 4500 to block 4418. Alternatively, if the userselects the third link or button 4506, the web-based program can receivea signal indicative of this selection and advance the process 4500 toblock 4420. In the event the process 4500 advances to block 4418, ascreen similar to that of FIG. 16 can be displayed. The web-basedprogram can send a request to the server to retrieve any uncompletedapplications stored on the server or in the database that correspondwith the user, and this information can be communicated to the web-basedprogram and displayed accordingly. Alternatively, if the process 4500advances to block 4420, the web-based program can communicate in asimilar manner with the server and in turn display the status of acompleted application similar to that in FIG. 17.

In the event a new application is started and the process 4400 advancesto block 4406, the web-based program can execute a start applicationmodule. The start application module can be stored in the server ordatabase. In any event, the module can be executed by displaying a startapplication screen 4600 similar to that in FIG. 46. Here, the module candisplay on the screen 4600 a first block of information 4602 thatidentifies what information may be required to complete the applicationprocess (i.e., owner name and contact information, buyer name andcontact information, etc.), a second block of information 4604corresponding to what to expect with the process 4400, and a third blockof information 4606 that includes an acknowledgement section whereby theuser is asked to review privacy policy and terms of service and confirmsuch review. This screen 4600 further provides the user with a statusblock 4608 that displays a timeline or list of steps for completing theapplication. Moreover, the start application module can provide the userwith a link or mechanism to ask questions during the process byselecting either customer support or selecting “information icons”located throughout the process on different screens.

The process 4400 can be structured such that it cannot advance pastblock 4406 until the user selects a check box or link in the third blockof information 4606 to acknowledge the privacy policy and terms ofservice. Until the user completes this action and the web-based program(or server) receives instruction that the user has made anacknowledgement, the process 4400 may not advance. Although not shown, a“next” or “continue” button may be displayed on the screen 4600 suchthat once the check box or link is selected, the process 4400 canadvance upon actuation of the “next” or “continue” button.

The process 4400 can then advance to block 4408 to request informationfrom the user about the transaction. An illustrative example of this isshown in FIG. 47. Here, a transaction screen 4700 can request atransaction amount 4702, identity of the user 4704 (e.g., buyer, seller,broker title company, third party, etc.), developer identity 4706, homeresort identity 4708, and owner number 4710 (if applicable). The screen4700 can be structured as a template similar to that described above inFIG. 25. In this manner, each item of information requested from theuser can be referred to as an input, and each input can be assigned acorresponding identifier. The identifier may be used later for executingthe necessary documents for completing the transaction, and also at theend of the process 4400 when the review screen is completed by theweb-based program.

As also shown in FIG. 47, the status block 4608 can be displayed on thescreen 4700. This is similar to as described above. The status block4608 can include a “save and quit” link or button 4712 to allow the userto save his or her progress at any point during the process 4400, andthen return later to complete the application. Upon saving theapplication, each input received by the web-based program can becommunicated to the server and a file can be created with acorresponding application number or identifier. The file can then besaved on the server or database. Upon executing block 4418, the servercan retrieve the file and communicate the contents thereof to theweb-based program so that the process 4400 can return to the block wherethe user exited.

Once the transaction information is received in block 4408, the process4400 can advance to block 4410 to collect information about transactionfees and the property. A screen 4800 similar to that in FIG. 48 can bedisplayed by the web-based program to request information from the userincluding unit number, building number, and week number, as applicable.An estimated fee for completing the transaction can be predetermined orcalculated by the web-based program based on the information provided inblock 4408. As such, the estimated fee due for the transaction can bedisplayed in a fee block 4802 in the screen 4800. The estimated fee canalso be adjusted if an additional unit or week is selected fromselectable link 4804. Here, if the transaction involves two or moreproperties or additional weeks, the user can select the link 4804 andadd additional units or weeks. A calculation module, similar to the onepreviously described, can be stored on the server, and based on theinputs received in blocks 4408 and 4410, the estimated fee can bedetermined.

The process 4400 can advance to block 4412 to further collectinformation about each party to the transaction. For example,information about an owner or seller as part of the transaction can berequested and received in block 4412. A screen similar to that of FIG. 9or 21 can be displayed for requesting this information. As previouslydescribed, the owner or seller screen can be a template stored on theserver or database and displayed to the user for collecting certaininformation. An identifier can link to each input received from the userfor later processing. Moreover, an address verification module stored onthe server, for example, can be executed to affirm the address receivedfor the owner or seller corresponds to a valid, known address by theU.S. Postal Office records. This module can be executed by a third partyand communications can be transferred between the web-based program andthe third party to receive the desired information.

Likewise, buyer or new owner information can be received in block 4412.A screen similar to that of FIG. 9 or 21 can be displayed to the userfor receiving the necessary information. The address verification modulecan be executed, and each input of information can be linked with acorresponding identifier for later use. In this manner, all inputinformation is linked or merged with a predefined identifier assimilarly described above. In addition, any documentation necessary forthe transaction can be collected. A documentation screen similar to thatof FIG. 11 may be displayed for receiving the necessary documentation.If a certain document is required for the transaction, a template ofthis document can be stored in a template library on the server ordatabase and thereby be provided to the user for execution. Forinstance, a document in which the seller authorizes the release ofinformation may be necessary. The template can include identifiers in itthat are linked to inputs received from the user, and thus the templatemay only require a signature, date, notarization, etc. for completion.Once completed, the user can then upload, email, fax, or mail thecompleted form. Instructions for completing this step can be provided ona screen similar to that in FIG. 11.

Once information for each party to the transaction is received, the filethat corresponds to the transaction or application can be updated andsaved to the server or database. Moreover, the process 4400 can advanceto block 4414 to execute a notification settings module. To execute thenotification settings module, an example of one screen 4900 is shown inFIG. 49. Here, the notification settings module can be retrieved fromthe server and request information including contact name, company name,email address, phone number, facsimile number, website, and address. Asa safety verification tool, the process 4400 can further verify theaddress against United States postal records. In the event a foreignjurisdiction is entered into the address blocks, further verificationcan be done to determine the accuracy and existence of such a postaladdress. If an address is not verified, the process 4400 may not be ableto advance past block 4414.

Contrary to screen 1200, the notification settings screen 4900 in FIG.49 may require a broker title company to disclose the closing companyfor the transaction. This may not be required in either process 300 or1800, but at least in one aspect of process 4400 the identity of theclosing company may be required. In other aspects, however, the closingcompany identity may not be required.

Once the inputs are received in block 4414, the web-based program canlink any remaining inputs with predefined identifiers. The file for thistransaction or application can be updated in block 4416 and a summary orreview template can be retrieved by the web-based program from theserver and link or merge all inputs to identifiers in the template. Thetemplate can be saved in the template library on the server or in thedatabase, and retrieved therefrom by the web-based program. Once thereview template is generated, it can be displayed to the user in ascreen 5000 similar to that in FIGS. 50A and 50B. FIGS. 50A and 50B canform a single screen 5000, but for purposes of clarity the screen 5000is separated to better illustrate some of the features displayed.

In the review screen 5000, each input collected from the user can bedisplayed once it is linked to or merged with a correspondingidentifier. Here, a transaction information block 5002 can display oneor more inputs received in blocks 4408 and 4410. Information collectedin block 4412 can be displayed in a current owner information block 5004and a new owner information block 5008. Moreover, information collectedin block 4414 can be displayed in a notification settings block 5006.Each of the aforementioned blocks in the screen 5000 can be selectablelinks such that any changes to inputs in a block can be updatedimmediately. For instance, if the current owner name is misspelled, theuser can select the current owner information block 5004 and the process4400 can return to block 4412 for further execution.

In the review screen 5000, a payment information block 5010 can displayany fees or payments that remain to be paid. To make any necessarypayment, the user may be presented with a payment window or block 1302similar to that in FIG. 13. In the event all fees and payments have beenreceived, such as shown in FIG. 50, the payment window or block 1302 maynot be displayed.

If the information displayed in the review screen 5000 is accurate andcomplete, and no further payment is needed, the user can select a checkbox and/or link in a “submit application” block 5012 to complete theapplication for requesting an estoppel. Each input received from theuser can be saved to the transaction file to the server or database, andthe corresponding estoppel application can be processed according tothose means known by one skilled in the art.

Once information in the review screen 5000 is affirmed, the web-basedprogram can advance the process 4400 to block 4422 to execute a documentgeneration module. The document generation module can be stored on theserver or in a database such that documents such as an AssessmentCertificate and Estoppel Letter, for example, can be generated. Otherdocuments may also be generated in this block 4422. Each document caninclude one or more identifiers such that each identifier is merged withan input received during the execution of the process 4400.

Referring to FIG. 77, an Assessment Certificate and Estoppel lettertemplate 7700 is shown. The template 7700 can include a plurality ofidentifiers as shown. For example, a first block or section 7702 caninclude one or more identifiers associated with the closing company.Inputs corresponding to the broker title company can be merged into thetemplate 7700 in this first section 7702. Similarly, a second block orsection 7704 can include one or more identifiers associated with theseller. Inputs corresponding to the seller can be merged into thetemplate 7700 in this second section 7704.

In the template 7700, the seller name can be linked to a seller nameidentifier (<<sellerNames>>) 7706, the buyer name can be linked to abuyer name identifier (<<buyerNames>>) 7708, and a purchase price can belinked to a purchase price identifier ($<<salesPrice>>). The purchaseprice input can be received in either block 4408 or 4410. Similarly, aresort information section 7712 can be positioned in the template 7700to merge resort input data with corresponding identifiers. The resortinput data may be received in one or more of the blocks of process 4400,or in one of the processes described in another embodiment of thepresent disclosure.

The template 7700 may also link input data related to current fees due,past fees due, and resort transfer fees. The current fees due input datacan be merged with identifiers in a current fees due section 7714, thepast fees due input data can be merged with identifiers in a past feesdue section 7716, and resort transfer fees input data can be merged withidentifiers in a resort transfer fees section 7718 of the template 7700.The template 7700 can also link a mailing address (<<mailingAddress>>)to a designated agent along with the agent's signature (e.g.,<<signingAgent>>) and date of signature (e.g., <<eDate>>). Other inputdata can be merged into this document as necessary. In addition, otherdocuments can be produced in block 4418 in a similar manner as theAssessment Certificate and Estoppel Letter described herein.

In this disclosure, files, templates, modules, programs, etc. can bestored on a web server or in a database. In some instances, more thanone database can be used. For example, one database can be used to storeinformation related to the processes 300, 1800 for transferring atimeshare. A second database may be used for storing information andfiles related to the process 4400 for requesting an estoppel. Anotherdatabase can be used to store the templates for closing documents, etc.such as those described in process 2500. Thus, while only one databasemay be described herein, it is to be understood that multiple databasescan be used to store files, information, programs, instructions, logic,modules, templates, etc.

In a different embodiment of this disclosure, a process for holding anescrow is provided. In this embodiment, an application for holding anescrow can be completed by a user logging into a web portal system orweb-based program similar to those previously described. In one example,a web-based program at http://www.Holdmyescrow.com can be accessed andcompleted. The process can include a series of blocks or steps that areorganized into an algorithm or set of instructions stored on a serverand executed by a web-based program at the aforementioned URL.Alternatively, the process can be stored as a program or set ofinstructions in a memory unit of a computing device or controller, andexecuted by a processor of the computing device or controller. Anexample of a process 5100 for requesting a hold of escrow is shown inFIG. 51.

Referring to FIG. 51, the process 5100 can advance to a first block 5102in which the web-based program can execute a welcome screen module. Thewelcome screen module can be stored on a server and display a screensimilar to that shown in FIG. 45. For instance, the user can bepresented with a plurality of options for advancing beyond the welcomescreen. For example, the user can select to start a new application,finish an existing application, or check a status of a completedapplication. Similar to the welcome screen of FIG. 45, the user may alsolog into their file, which can be stored on the server or database. Inaddition, a user may access customer support or otherwise seek help.

The process 5100 can advance past block 5102 based on the instructionsent by the user to the web-based program from the welcome screen. Here,in block 5104, the web-based program receives an instruction orcommunication from the user and the instruction is processed andexecuted by completing one or more additional blocks or steps in theprocess 5100. For example, if the user selects to start a newapplication, the process 5100 can advance to block 5106. If, however,the user instructed the web-based program to finish an existingapplication, the process 5100 can advance to block 5108. Moreover, ifthe user instructed the web-based program to retrieve completedapplications corresponding to the user's account, the process 5100 canadvance to block 5110. Block 5108 can be carried out similar to that ofblock 4418 as previously described. In addition, block 5110 can beexecuted similar to that of block 4420 of FIG. 44.

In block 5106, the web-based program is configured to execute a startapplication module. This module can be stored on the server or in thedatabase on the server. In any event, the module can provide the userwith a plurality of options. In FIG. 55, for example, a new escrowapplication can be executed by presenting the user with a plurality ofdifferent applications to complete. A screen 5500 can be displayed thatpresents these options to the user. The user may execute a new rentalapplication, a new sale application, or a broker application. To preparea new rental application, the display includes a first link 5502 thatcan be selected by the user to advance to a rental application process5200. To prepare a sale application, the display can include a secondlink 5504 that can be selected by the user to advance to a saleapplication process 5300. In addition, to prepare a broker application,the display can include a third selectable link 5506 for advancing to abroker application 5400.

Once the user selects one of the options, the process 5100 can advanceto blocks 5112, 5114, and 5116 to determine which application the userselected. If the process 5100 determines that the new rental applicationis selected, in block 5112 the process 5100 can advance to the rentalapplication process 5200 shown in FIG. 52. If, however, the process 5100determines that the new sale application is selected in block 5114, theprocess 5100 can advance to the sale application process 5300 shown inFIG. 53. Moreover, if the process 5100 determines that the new brokerapplication is selected in block 5116, the process 5100 can advance tothe broker application process 5400 shown in FIG. 54.

A new rental application can be completed according to the process 5200shown in FIG. 52. The process 5200 can begin with a first block 5202 forexecuting a start rental application module. In this module, a screen5600 similar to the one in FIG. 56 can be displayed for the user. Thescreen 5600 can be arranged similarly as the screen 4600 in FIG. 46. Thescreen 5600 can be predefined and stored on the server or database. Inthe screen 5600, the process 5200 can set forth items needed to completethe application, what the user can expect by completing the application,and a link to the privacy policy and terms of service. The screen 5600can also include a “start application” or “continue” button for the userto select and advance the process 5200 to the next block. The web-basedprogram 5200 may not advance unless a check box is marked or selected bythe user before selecting the “start application” or “continue” button.

Once the start rental application module has been executed in block5202, the process 5200 can advance to block 5204 to collect transactioninformation from the user. In block 5204, the process 5200 can requestinformation in a screen 5700 as shown in FIG. 57. In this screen 5700,an application status window or box can be displayed to show the userwhere in the process 5200 the user currently is. This is similar to theapplication status windows or boxes described previously in thisdisclosure. In addition, block 5204 can request information such astransaction type 5704 (e.g., rental, sale, broker), transaction amount5706, party identity 5708 (e.g., lessee, lessor), resort name 5710, unitnumber or numbers 5712, and week number or numbers 5714. Based on thisinformation, the web-based program can provide the user with anestimated amount for an escrow fee 5716 as shown in FIG. 57. Once thisinformation is provided by the user, the inputs received by theweb-based program can be used to produce a transaction file. The inputsmay be transferred to the web-based program or the server once the userselects a “Next” or “continue” button from the screen 5700. In anyevent, once the inputs are received and placed in the transaction file,the transaction file can be stored on the server or database.

Once block 5204 is completed, the process 5200 can advance to block 5206to collect information about each party to the transaction. In a rentalagreement, information may be requested of the lessor and lessee. Thisinformation can include name, address, email address, home phone number,work phone number, cell phone number, employer, employer address, etc.Similar to the modules described above, the address of each party can beverified by confirming with the U.S. Postal Office records. If theaddress is unfound or not confirmed as valid, the process 5200 (like thepreviously described processes) may not advance until a valid address isprovided.

In each block, information received from the user may be linked with anidentifier similar to that described above with respect to process 2500.In this manner, many of the screens can directly link an input with anidentifier, and this can be saved to the server or database. Each inputis linked with its corresponding identifier in block 5208, and as such areview template can be pulled from a template library stored on theserver or database. Each input can be linked or merged in the reviewtemplate, and the template can then be displayed to the user in a screen5800 similar to that shown in FIGS. 58A and 58B. Similar to the screen5000 in FIGS. 50A and 50B, the screen 5800 is separated into FIGS. 58Aand 58B to better illustrate some of the features displayed therein. Thereview screen 5800 can identify the transaction information 5802received from the user in block 5204, lessor information 5804 receivedin block 5206, and lessee information 5806 received in block 5206.Moreover, payment information, e.g., the escrow fee, can be displayed ina payment window 5808 and a verification block 5810 can be provided forthe user to select a check box or link to verify the completeness andaccuracy of the information shown in the review screen 5800. Once theuser affirms this information and submits the application, the process5200 can advance to an application processing block 5210. Theapplication can be stored in the database or server during thisexecution of this block 5210.

In another aspect, if the user selects a sale agreement in block 5114, asale application process can be executed. The sale application processcan be stored on the server and executed by the web-based program. InFIG. 53, one example of a sale application process 5300 is shown. Theprocess 5300 can begin with a first block 5302 for executing a startsale application module. In this module, a screen 5900 similar to theone in FIG. 59 can be displayed for the user. The screen 5900 can bearranged similarly as the screen 4600 in FIG. 46 and the screen 5600 inFIG. 56. The screen 5900 can be predefined and stored on the server ordatabase. In the screen 5900, the process 5300 can set forth itemsneeded to complete the application, what the user can expect bycompleting the application, and a link to the privacy policy and termsof service. The screen 5900 can also include a “start application” or“continue” button for the user to select and advance the process 5300 tothe next block. The process 5300 may not advance unless a check box ismarked or selected by the user before selecting the “start application”or “continue” button.

Once the start sale application module has been executed in block 5302,the process 5300 can advance to block 5304 to collect transactioninformation from the user. In block 5304, the process 5300 can requestinformation in a screen 6000 as shown in FIG. 60. In this screen 6000,an application status window or box 5702 can be displayed to show theuser where in the process 5300 the user currently is. This is similar tothe application status windows or boxes described previously in thisdisclosure.

In addition, in block 5304 the process 5300 can request information suchas transaction type 6002 (e.g., rental, sale, broker), transactionamount 6004, party identity 6006 (e.g., owner, buyer, third party),resort name 6008, unit number or numbers 6010, and week number ornumbers 6012. Based on this information, the web-based program canprovide the user with an estimated amount for an escrow fee 6012 asshown in FIG. 60. Once this information is provided by the user, theinputs are received by the web-based program and a transaction file canbe produced and saved on the server. The inputs may be transferred tothe web-based program once the user selects a “Next” or “Continue”button from the screen 6000. In any event, once the inputs are receivedand placed in the transaction file, the transaction file can be storedon the server or database.

Once block 5304 is completed, the process 5300 can advance to block 5306to collect information about each party to the transaction. In a saleagreement, information may be requested of the owner, buyer, and/or athird party. In some agreements, a real estate agent, broker, or otherparty may be a party to the transaction. This information can includename, address, email address, home phone number, work phone number, cellphone number, employer, employer address, etc. Similar to the modulesdescribed above, the address of each party can be verified by confirmingwith the U.S. Postal Office records. If the address is unfound or notconfirmed as valid, the process 5300 (like the previously describedprocesses) cannot advance until a valid address is provided.

In each block, information received from the user may be linked with anidentifier similar to that described above with respect to processes2500 and 5200. In this manner, many of the screens can directly link aninput with an identifier, and this can be saved to the server ordatabase. Each input is linked with its corresponding identifier inblock 5308, and as such a review template can be pulled from a templatelibrary. Each input can be linked or displayed in the review template,and the template can then be displayed to the user in a screen 6100similar to that shown in FIG. 61. The review screen 6100 can identifythe transaction information 6102 received from the user in block 5304,owner information 6104 received in block 5306, third party information6106 received in block 5306, and buyer information 6108 received inblock 5306. Moreover, payment information, e.g., the escrow fee, can bedisplayed in a payment window 6110 and a verification block 6112 can beprovided for the user to select a check box or link to verify thecompleteness and accuracy of the information shown in the review screen6100. Once the user affirms this information and submits theapplication, the process 5300 can advance to an application processingblock 5310. The application can be stored in the database or on theserver during the execution of block 5310.

Returning to FIG. 51, if the user selects a broker agreement in block5116, a broker application process can be executed. In FIG. 54, oneexample of a broker application process 5400 is shown. The process 5400can be stored as a web-based program on the server and begin with afirst block 5402 for executing a start broker application module. Inthis module, a broker may be required to login or sign into the webportal as previously described. In this instance, a file may already bestored for a given login in the database or on the server. Once logininformation is submitted, the information can be linked with theexisting file. In the event the broker does not already have a file, thebroker may be requested to register or create a file similar to thatpreviously described.

If the broker does have a file, once login information is received andthe file is retrieved, account information corresponding to the logininformation can be displayed in a screen 6200 similar to that in FIGS.62A and 62B. The screen 6200 can include a plurality of features andtherefore the screen 6200 is shown partially in FIGS. 62A and 62B tobetter illustrate these features. In the screen 6200, the web-basedprogram can display in an application window 6202 any existingapplications previously started or completed by the user whichcorrespond with the login information. In FIG. 62, there are noapplications that have been started for this particular logininformation. If an application is shown in this window 6202, theapplication can be displayed based on its application number oridentification, its status, type of application (e.g., rental, sale, orbroker), order number, last name of one party, date application wassubmitted, and any options that may be exercised with this application.For example, if the application was not complete, the user may be ableto open the application and complete it.

The screen 6200 can also provide a drop-down menu 6204 for the user toselect other options related to the applications. For instance, a brokermay have one application for one particular developer or resort andanother application for a different developer or resort. The drop-downmenu 6204 can allow the user to access different applications fordifferent developers or resorts. Other options may be available as wellfrom this menu.

The screen 6200 can further provide the broker or user with an option tostart a new application in a new application window 6206. This issimilar to the screen 5500 in FIG. 55. Here the user can select to starta new rental agreement, a new sale agreement or a new broker agreement.If the new rental agreement or application is selected by the user, theprocess 5400 ends and the web-based program executes the rentalapplication process 5200 of FIG. 52. Likewise, if the new sale agreementor application is selected by the user, the process 5400 ends and theweb-based program executes the sale application process 5300 of FIG. 53.If, however, the user selects the new broker application, the process5400 continues executing the start broker application module in block5402. For instance, similar to FIGS. 56 and 59, the process 5400 can setforth items needed to complete the application, what the user can expectby completing the application, and a link to the privacy policy andterms of service. The screen can also include a “start application” or“continue” button for the user to select and advance the process 5400 tothe next block. The process 5400 may not advance unless a check box ismarked or selected by the user before selecting the “start application”or “continue” button.

Once the start broker application module, which can be stored on theserver, has been executed in block 5402 the process 5400 can advance toblock 5404 to collect transaction information from the user. In block5404, the process 5400 can request information in a screen 6300 as shownin FIG. 63. In this screen 6300, an application status window or box5702 can be displayed to show the user where in the process 5400 theuser currently is. This is similar to the application status windows orboxes described previously in this disclosure. In addition, in block5404 the process 5400 can request information such as transaction type6302 (e.g., rental, sale, broker), transaction amount 6304, and partyidentity 6306 (e.g., seller, buyer, third party). Other information maybe requested from the user other than that shown in the screen 6300.Based on this information, the web-based program can provide the userwith an estimated amount for an escrow fee 6308 as shown in FIG. 63.Once this information is provided by the user, the inputs are receivedby the web-based program and a transaction file can be produced. Theinputs may be transferred to the server or the web-based program oncethe user selects a “Next” or “Continue” button from the screen 6300. Inany event, once the inputs are received and placed in the transactionfile, the transaction file can be stored on the server or database.

Once block 5404 is completed, the process 5400 can advance to block 5406to collect information about each party to the transaction. In a brokerapplication, information may be requested of the seller and third party.In some applications, a real estate agent, broker title company, orother party may be a party to the transaction and information about thisparty is requested. This information can include name, address, emailaddress, home phone number, work phone number, cell phone number,employer, employer address, employer website, etc. Similar to themodules described above, the address of each party can be verified byconfirming with the U.S. Postal Office records. If the address isunfound or not confirmed as valid, the process 5400 (like the previouslydescribed processes) cannot advance until a valid address is provided.

In each block, information received from the user may be linked ormerged with an identifier similar to that described above with respectto processes 2500, 5200, and 5300. In this manner, many of the screenscan directly link an input with an identifier, and this can be saved tothe application file and/or to the web-based program, server ordatabase. Each input is linked with its corresponding identifier inblock 5408, and as such a review template can be pulled from a templatelibrary stored on the server or database. Each input can be linked ordisplayed in the review template, and the template can then be displayedto the user in a screen 6400 similar to that shown in FIGS. 64A and 64B.The screen 6400 can include a plurality of features and therefore thescreen 6400 is shown partially in FIGS. 64A and 64B to better illustratethese features. The review screen 6400 can identify the transactioninformation 6402 received from the user in block 5404, sellerinformation 6404 received in block 5406, and third party information6406 received in block 5406. Moreover, payment information, e.g., theescrow fee, can be displayed in a payment window 6408 and a verificationblock 6410 can be provided for the user to select a check box or link toverify the completeness and accuracy of the information shown in thereview screen 6400. Once the user affirms this information and submitsthe application, the process 5400 can advance to an applicationprocessing block 5410. The application can be stored in the database orotherwise on the server during the execution of block 5410.

Depending on the type of transaction being executed in process 5100,documents can be generated in a document generation module similar tothat of FIG. 44. A first example of this is shown in FIG. 78 where aResale Transfer Agreement can be produced from a template 7800 stored onthe server. In the template 7800, an escrow file number can be createdby the web-based program or server and linked with a correspondingidentifier 7802. Input data related to a broker title company can belinked with identifiers in a first section 7804 of the template, wherethe identifiers correspond to a broker company name, address, phonenumber, fax number, email address, and website URL. Input data relatedto a seller can be linked with identifiers in a second section 7806 ofthe template 7800, where the identifiers correspond to seller name,address, phone number, fax number, and address. Input data can also bereceived for an escrow agent and linked with identifiers (not shown) ina third section 7808. Moreover, a timeshare resale transfer price can bemerged into the template and linked with an identifier 7810corresponding to a timeshare resale transfer (e.g., <<salesPrice>>).

The template 7800 of FIG. 78 can be stored on the server or in adatabase on the server. It may also be stored in another memory deviceor other location that is in communication with the server. Otherinformation can be merged into the template 7800 such as an escrow agentfees for services provided by the escrow agent. Other documents cantherefore be produced in the document generation module based on thetype of transaction being executed.

A second example of a template 7900 used to generate a document in theprocess 6500 is shown in FIG. 79. The template 7900 can be used toproduce a sale and escrow agreement. Here, input data corresponding toseller or owner information and buyer or renter information can belinked with predefined identifiers and thereby merged into theappropriate locations in the template 7900. For example, a seller orowner name can be linked with an identifier 7902, <<sellerName1>> and<<sellerName2>>. Similarly, a buyer or renter name can be linked with anidentifier 7904, <<buyerName1>> and <<buyerName2>>. Moreover, buyer orrenter information can be linked with identifiers in a first informationsection 7906 and seller or owner information can be linked withidentifiers in a second information section 7908. Other information canbe linked with corresponding identifiers and merged into the template7900 to produce the desired document. For example, an escrow amount due(<<salesPrice>>), purchase and sale of Property (e.g.,<<transferPurposeSaleX>>), rental of property (e.g.,<<transferPurposeRentalX>>), resort name (e.g., <<resortNameText>>),unit number (e.g., <<unitNumberText>>), week number (e.g.,<<weekNumberText>>), and escrow fee (<<billableCostCunent>>).

As documents are produced in the document generation module, thedocuments can be transferred to each party for review and execution. Aletter formed from a letter template stored on the server can beproduced as well, which can provide instructions to each respectiveparty about the transaction and the document produced. Once documentsare executed by each party and returned to the server, instructions maybe stored on the server to further complete blocks 5210, 5310, or 5410by submitting executed documents to a government authority or otherthird party for purposes of completing the transaction process.

In a different embodiment of the present disclosure, a process isprovided for handling a real estate transaction between one or moreparties. In this embodiment, a real estate sales professional, forexample, can use standard customizable, standard real estate documentsas templates to prepare high quality, professional real estate salescontracts. Similar to the other processes described in this disclosure,the process can be accessed over the network through a web-basedapplication or program. In one example, an independently distinct URL orwebsite may be available for completing the process. One such examplemay be found at http://www.jiffydocs.com. Alternatively, the web-basedprogram may be stored on a web server, database, computing device or viadownloadable software. Information can also be stored on the internet,on the server, or in the database.

An example of one process 6500 is shown in FIG. 65. The process 6500 caninclude a plurality of blocks or steps for executing to complete anapplication process and transfer a transaction. During the process 6500,templates and other control modules can be stored on a server or in adatabase and communicated to the web-based program which can becontrolled by a web server. For purposes of this disclosure, the serverand web server can be considered the same. The server or database canalso store templates and other documents or files in a template library.In some instances, each template can be unique to a registered user andstored in the template library for use during execution of the process6500 by the user. In other instances, predefined templates or forms canbe stored in a memory device, a second database, or in another locationthat is in electrical communication with the server and web-basedprogram. Information, calculations, and other communications can occurbetween the database, server, and web-based program over the network forexecution of the process 6500. This can be similar to the otherprocesses described herein.

In FIG. 65, the process 6500 can execute a first block 6502 byrequesting a login from a user via a login screen. As previouslydescribed in other embodiments, a user may be a buyer, seller, thirdparty, etc. that first accesses the process 6500 via the internet. Awebsite address or web portal for executing this process 6500 canprovide a plurality of options. In any event, a user that desires tostart a new application, complete an existing application, or check astatus of a previously completed application may be required to firstlogin to the web portal similar to that in FIG. 4. If a first-time useraccesses the web portal, instructions may be provided by the process6500 in block 6502 for registering an account. A new account templatemay be uploaded from the server or database and request the user toprovide information related to the account. This may include an emailaddress, user name, name, address, date of birth, company name,password, etc. Once an account is created, the account number or filecan be stored on the server or database.

A returning user may simply be required to login to advance the process6500. Once a user submits login information to the system, the logininformation can be sent to the server to locate the registered useraccount information in block 6504. The login information may be storedon the server or in a database electrically coupled to the server. Onceaccount information is located, the process 6500 can display a screen6600 similar to that in FIG. 66. In screen 6600, the account informationcan be displayed in the web-based program related to the located file.As shown, the screen 6600 can display information for one or moreapplications stored for the registered user in an application block6602. This information can include application number or identification,application status, application type, order number, last name of party,date application submitted (if applicable), and any option or optionsavailable to the user. In the event a user wants to start a newapplication, a new application link or button 6604 is provided on thescreen 6600 for the user to select.

Upon logging into the web portal and selecting the new application linkor button 6604, a signal can be received by the web-based program toadvance the process 6500 to block 6506 to execute a start real estatesale application module. Since the web-based program can be stored onthe server, the signal can also be or alternatively be received by theserver. In this block, the web-based program, can retrieve any templatesstored for the given user based on login information and accountidentification. These templates may have been previously downloaded bythe user to the server and stored in a template library, or thetemplates may have been downloaded or transferred to a database on theserver or in communication with the server. In any event, the process6500 can locate and retrieve all templates associated with the logininformation received in block 6502.

Upon locating any templates associated with the login information, theprocess 6500 can advance to block 6508 to execute a sale informationmodule. An example of this is further shown in FIG. 67. Here, theweb-based program can execute block 6508 by displaying a saleinformation template or screen 6700. In the screen 6700, a plurality ofinformation or text boxes are provided for receiving input from theuser. For instance, a first plurality of information or text boxes 6704requests information from the user including an advertising number, acontract date, a seller acceptance date, an estimated closing date, anestimated closing fee, and an administrative fee. In a second pluralityof information or text boxes 6708, the sales information module requestsinputs such as purchase price, deposit amount, and total commissionamount. In a third plurality of information or text boxes 6714,information is requested from the user including sales agent and salesagent email address. In a fourth information or text box 6718, the saleinformation module requests information about the closing company. Theinformation requested from each text box is only provided as oneexample, however, and other sale information modules may requestaddition or different information. For instance, the sale informationmodule may exist as a template provided by the user and stored on theserver such that the user can customize the template to request any typeor form of information necessary in this block.

In FIG. 67, the sale information module also includes calculationmodules for calculating different fees. For example, a first calculationmodule 6706 is shown in FIG. 67 for determining a total estimatedclosing cost. The first calculation module 6706 may be structured tocompute the total estimated closing cost based upon the inputs receivedin the first plurality of information or text boxes 6704. In onenon-limiting example, the total estimated closing cost may be asummation of the estimated closing fee and the administrative fee. Inother examples, this calculation may differ based on the type ofinformation received in the first plurality of information or textboxes.

A second calculation module 6710 can also be provided in the saleinformation module for determining a net fee due to the seller. The netfee due to seller may be computed by the second calculation module 6710based upon the inputs received in the second plurality of information ortext boxes. In one non-limiting example, the net fee due to seller maybe computed as the difference between the purchase price and totalcommission amount. In other examples, however, other inputs can be takeninto consideration to determine the net fee due to seller.

A third calculation module 6712 can be provided in the screen 6700 todetermine a cash amount due on closing. In this module 6712, the cashamount due on closing may be determined based on the inputs receivedfrom one of the first or second plurality of information or text boxes.In one non-limiting example, the cash amount due on closing may becomputed by calculating the difference between the purchase price anddeposit amount. In other examples, the cash amount due on closing maydiffer based on the type of inputs received in the sale informationmodule. Each of the aforementioned calculation modules can be stored onthe server or in a database in communication with the server.

As will be described with reference to block 6520, each input receivedin the sale information module can be linked or associated with anidentifier. For example, a purchase price may be linked with anidentifier such as ${PurchasePrice}. This identifier may therefore beused to merge the purchase price input received in the second pluralityof information or text boxes 6708 from the user to any location in oneor more templates, calculation modules, or documents as part of adocument generation module in block 6524 (which will be explained ingreater detail below). Thus, to generate or produce a sales contract orother document, any template that includes the identifier${PurchasePrice} will be linked or merged with the input received fromthe user during execution of block 6508. This same process may be usedin the other blocks of the process 6500 as well.

As also shown in the screen 6700 of FIG. 67, a status bar or window 6702may be displayed to show the user visually where in the process 6500 theuser currently is. It may also show completed steps or blocks anduncompleted steps or blocks. The server can continuously update thestatus bar or window 6702 by communicating with the web-based program asthe process 6500 is executed. This is similar to thepreviously-described status windows or blocks.

In addition, the sale information module can request information aboutwhether the transaction is a co-broker transaction. This is shown in theco-broker transaction input box 6716 in FIG. 67. Here, the user canselect or instruct the web-based program about whether a co-broker isinvolved in the transaction. In the event a co-broker transaction isselected affirmatively by the user, a signal is submitted to theweb-based program and the server can advance the process 6500 to block6510. In block 6510, the process 6500 can execute a co-broker module bycollecting or requesting information about a co-broker. An example ofthis is shown in a screen 6800 in FIG. 68. In the co-broker module, thescreen displays an input section 6802 where the user is asked to provideinformation including co-broker company name, co-broker phone number,co-broker agent, co-broker sales agent's email address, co-brokerscommission, and co-broker administrative fee. Other information may berequested from the co-broker module of the user, and as such FIG. 68 isonly one example. The module may also include a calculation module 6804for computing a commission due to a broker. This calculation may bebased upon the inputs received in the input section 6802 of screen 6800.Alternatively, the calculation may be based upon inputs received inblocks 6508 and 6510. Once this information is received and thecalculation is completed in the calculation module 6804, the process6500 may advance to block 6512.

If, however, this transaction does not involve a co-broker, the process6500 can skip block 6510 and advance to block 6512. In any event, onceeither block 6508 or block 6510 is executed, the process 6500 canadvance to block 6512 to execute a resort information module. In theresort information module, a screen 6900 such as the one shown in FIG.69 can be displayed to the user for requesting information about aresort involved in the transaction. In this screen 6900, the resortinformation module can request resort name, resort state, buildingnumber(s), unit number(s), lockout information, unit week(s), week type,size of property (number of bedrooms, bathrooms, square footage,amenities, etc.), unit season, unit occupancy, unit view, availableoptions, resort transfer fee, and exchange company (if applicable). Thisis only one example, however, and other resort information modules mayrequest different or additional information. Once inputs are receivedfrom the resort information module in block 6512, the process 6500 canadvance to block 6514. The resort information module can be stored onthe server or in a database in communication with the server.

In block 6514, a transaction information module is executed. Thetransaction module can be stored on the server or in a database andexecuted by requesting information about the transaction from the user.An example of this is shown in FIG. 70. Here, a transaction informationscreen 7000 provides a plurality of information boxes for receivinginputs from the user. In a first input section 7002, information such asnumber of bedrooms, number of bathrooms, annual maintenance fees, andfirst year of use can be collected. Additional or different informationmay be collected in this first input section 7002.

In a second input section 7004, the module can request which party willpay current maintenance fees. The module can provide options includingbuyer, seller, split between buyer and seller, or buyer reimburseseller. This is similar to a third input section 7006 in which themodule requests which party will pay previous maintenance fees. Otheroptions may exist, including none if there are no current or previousmaintenance fees due.

In a fourth input section 7008, the module can request informationregarding a reimbursement amount due to seller. In a fifth input section7010, the module can request information about how title will be vestedafter the transaction is completed. The fifth input section 7010 caninclude options such as a single man or woman, a married man or woman,tenants in common, joint tenants with right of survivorship, and marriedcouple (e.g., husband and wife, domestic partners, etc.). Once thisinformation is received from the user, the process 6500 may advance toblock 6516.

In block 6516, the web-based program can collect reservation informationfor the transaction. An example of this is shown in FIG. 71. Here, theweb-based program can collect reservation information from a reservationscreen 7100 that requests information such as reservation date 7102,confirmation number 7104, verified with information 7106, and verifieddate 7108. This screen or a variant thereof may be stored on the server.In this block, a transaction may be consummated when the seller orcurrent owner has a previously-arranged reservation for a given periodof time. The parties to the transaction may agree as to which party isable to hold the reservation, and this may be designated in FIG. 71 in areservation box 7110. Once the reservation inputs are received in block6516, the process may advance to block 6518.

In block 6518, the process 6500 can execute a party information module.Here, the party information module can collect information from the userabout the seller(s) and buyer(s). In FIG. 72, for example, a screen 7200is provided for requesting information about a seller in thetransaction. The screen 7200 may be formed as a template stored on theserver and displayed to the user on an electronic computing device. Thisinformation can include name, address, email address, home phone number,work phone number, cell phone number, employer, employer address,employer website, etc. Similar to the previous embodiments of thisdisclosure, the address of the seller can be verified by confirming withthe U.S. Postal Office records. If the address is unfound or notconfirmed as valid, the process 6500 (like the previously describedprocesses) cannot advance until a valid address is provided. Moreover,if the transaction includes two or more sellers, the screen 7200 canprovide an option 7202 for adding another seller. If a second oradditional seller is added, a screen similar to that of FIG. 72 may bedisplayed to request information about the second or additional seller.

Similar to FIG. 72, the block 5406 can also request buyer information.An example of this is shown in FIG. 73. Here, a buyer information screen7300 can be displayed to request information about the buyer. Thisinformation can include name, address, email address, home phone number,work phone number, cell phone number, employer, employer address,employer website, etc. Similar to above, the address of the buyer can beverified by confirming with the U.S. Postal Office records. If theaddress is unfound or not confirmed as valid, the process 6500 (like thepreviously described processes) cannot advance until a valid address isprovided. Moreover, if the transaction includes two or more buyers, thescreen 7300 can provide an option 7302 for adding another buyer. If asecond or additional buyer is added, a screen similar to that of FIG. 73may be displayed to request information about the second or additionalbuyer.

Once the party information module is completed and information requestedof the seller and buyer is received in block 6518, the process 6500 canadvance to block 6520 to link or merge inputs with identifiers in areview application template. The review application template can be acustomizable template that is provided and used exclusively by the user,or it may be a general template stored on the server or a database in atemplate library. Any template uploaded or otherwise provided by theuser may be stored on the server or in a database in a template libraryalong with other templates. A folder of templates may be stored in thetemplate library whereby the folder is associated with the logininformation received in block 6502. As such, the server can retrieve oneor more templates from the folder of templates based on the type ofinputs received by the server during execution of the process 6500. Inany event, each input received in the process 6500 can be linked with aunique, predefined identifier in a manner similarly described in theprevious embodiments. For instance, a seller name input received fromthe user may be linked with unique identifier ${SellerName} in thereview application template in block 6520.

Once each input is linked to or merged with its identifier in block6520, the review application template can be displayed to the user forreview. An example of a review application template 7400 is shown inFIG. 74. In the template, a plurality of information boxes or areas areprovided to summarize the information received during the process 6500.For example, a sale information box 7402 can structurally display theinputs received in block 6508. In addition, a seller information box7404 and buyer information box 7406 can structurally arrange theinformation received in block 6518 as shown in FIG. 74. Moreover, aco-broker information box 7408 can display information as received inblock 6510, a resort information block 7410 can display informationreceived in block 6512, and a reservation information box 7414 candisplay information as received in block 6516. In each box, thedisplayed information can be a result of receiving an input from theuser during the application process 6500 and linking the input with anindependent, unique identifier. The input can then be placed or arrangedin the review application template 7400 in a position similar to thatshown in the screen 7400 of FIG. 74. This provides an organized,structured review screen 7400 for the user to review all informationpreviously input to the web-based program.

The review application template screen 7400 can also provide a link orbutton 7416 along with an instruction for the user to return to aprevious block in the process 6500 in the event an input is incorrect orneeds to be revised. Since each information box includes informationlinked to a certain block in the process 6500, the web-based program canreturn to the user to the desired block to make the desired change inthe application.

The review application template screen 7400 can further provide averification link or button 7418 whereby the user can select this linkor button to complete the application process. A check box or similaraction mechanism may be displayed for the user to click or otherwiseacknowledge that the information displayed in the review applicationtemplate screen 7400 is accurate and complete. Upon actuating this link7418, the process 6500 can advance to block 6522 to execute theapplication processing module.

The application processing module in block 6522 can display a screen7500 similar to that in FIG. 75. The screen 7500 can be an instructionscreen stored as a template on the server or database in the templatelibrary. In any event, the screen 7500 can provide instructions, followup steps, or general expectations now that the application has beensubmitted for processing. At the same time or after a user acknowledgesthe instruction screen 7500 in FIG. 75, the process 6500 can advance toblock 6524 to execute a document generation module.

The document generation module is similar to that described in theprocess 2500 above. For example, a purchase agreement, a net listingagreement, and an authorization to release information to a titlecompany may be produced in block 6524. An example of a purchaseagreement template 7600 is shown in FIG. 76. In the template 7600, aplurality of inputs received in the process 6500 can be linked intospecific locations in the purchase agreement template. For instance, afirst input (or group of inputs) 7602 corresponds with a buyer andseller names, which are requested in the party information module ofblock 6518. A second input (or group of inputs) 7602 corresponds with adescription of the property, which is requested in the resortinformation module of block 6512 and the transaction information moduleof block 6514. A third input (or group of inputs) 7606 is related to theparty name to be disposed on the deed. This information is requested inthe transaction information module of block 6514 of the process 6500,and the party information module of block 6518.

The template 7600 can also include a fourth input (or group of inputs)7608 that corresponds to purchase price, deposit held in escrow, andcash due on closing. Each of these inputs can be requested in the saleinformation module in block 6508. A fifth input (or group of inputs)7610 corresponds to a closing date, which is also requested in the saleinformation module of block 6508. A sixth input (or group of inputs)7612 in the template 7600 can relate to which party is responsible forpaying current year maintenance fees and taxes. This information iscollected in the transaction information module of block 6514 and eachinput can be linked to or merged with a corresponding identifier in thetemplate 7600 as shown. Here, the buyer is responsible for payingcurrent year maintenance fees and taxes. Another input 7614 is shown inthe template 7600 corresponding to the date the contract is entered intoby the parties. This input is requested in the sale information moduleof block 6508.

The purchase agreement template 7600 can include other inputs which arelinked or merged in the template to form the purchase agreement. Onceeach input is linked to or merged into its respective location in thetemplate, the purchase agreement document can be generated in block6524. To execute the transaction process in block 6526, the purchaseagreement document can be sent to each party with instructions for eachparty to sign in the signature block area 7616 of the document. Here,each seller and buyer is requested to sign, and once the purchaseagreement is executed by each party and returned the document can befurther processed (e.g., submitted to the appropriate government officefor recording). Depending on the type of document, each party may beable to electronically sign and verify the accuracy and completeness ofinformation contained on a respective document without having to handlea physical document or form. Thus, communication between the web-basedprogram and each party may be handled electronically such that theserver can electronically transfer and receive documents to and fromeach party.

Other documents, depending on the type of transaction and type oftemplates a user may require for a given transaction, may be generatedin block 6524 similar to the purchase agreement. As described, once thenecessary documents are generated in block 6524, the process 6500 canadvance to block 6526 to complete the transaction process. In otherwords, the generated documents can be sent to the party or parties ofthe transaction for execution. As previously noted, this can occur viaemail, facsimile, mail or through other known means. Once executeddocuments are received, the server can control the web-based program tofurther facilitate the necessary filing and recording with governmentoffices or other actions necessary to complete the transaction.

Each of the aforementioned processes in this disclosure are describedindividually and, in most instances, described as being independent.However, as shown in FIG. 43, each process can be integrated into alarger process where two or more of these processes are executed tocomplete a desired transaction. Thus, this disclosure provides aplurality of different processes and document generation modules thatcan be tailored for the timeshare industry or real estate industry forthe production and execution of documents and forms necessary for aproperty transfer.

Moreover, the embodiments of the present disclosure are described andillustrated as a web based program that can be executed by a server.Documents, templates, modules, etc. can be stored on the server or in adatabase that is in communication with the server. The database, forexample, can be stored on the server. In any event, this disclosure isnot intended to be limiting in the sense that one or more of theembodiments described herein may be executed via a means other than aweb-based program and server. In at least one instance, a program orsoftware can be stored on a disk, memory device, or other electronicmeans. The program or software can execute each embodiment in a mannersimilar to that described in this disclosure.

Referring to a different embodiment illustrated in FIG. 80, a system8000 is shown of a main server 8002 upon which a program that includes aset of instructions for executing any of the previously describedprocesses is stored thereon. The server 8002 can be disposed inelectrical communication with one or more databases 8018. This issimilar to the embodiments of FIGS. 1 and 2 where the server 180 is inelectrical communication with a network 190 and database 260. Aspreviously described, the one or more databases 8018 may include atemplate library 8020 stored therein. The template library 8020 caninclude one or more templates that relate to a particular type oftransaction being executed, where each template can include one or moreidentifiers that corresponds with information received by the server8002 from a user.

Upon execution of any of the aforementioned processes, information canbe received by the server and stored either on the server 8002 or one ofthe databases 8018. From this point forward and for simplicity reasons,the present disclosure will refer to a database 8018 rather than one ormore databases, but it is intended to be understood that the database8018 can include more than one database.

The execution of the aforementioned processes can include execution of aset of instructions of a program by a processor of an electroniccomputing device. The electronic computing device can include theprocessor and a memory. The device can function on its own server andcommunicate over a network with the main server 1802.

The main server 1802 can also be in electrical communication with one ormore third party servers. For instance, in FIG. 80, the server 1802 isshown in electrical communication with a first third party server 1804,a second third party server 1806, and a third party server 1808. Eachthird party server can communication information back and forth with themain server 1802 over a network or other communication link.

In one example and as previously described, an at least one addressassociated with a party to a transaction can be obtained from executionof the party information module. This at least one address can becommunicated to a second server, e.g., one of the third party servers1804, 1806, 1808, associated with the postal service to verify that theat least one address associated with the party corresponds to a validaddress according to postal service records. As a second example,execution of the payment module can include communicating paymentinformation from the main server to another third party serverassociated with handling payments. This third party server maycorrespond to one of the third party servers disposed in electricalcommunication with the main server 1802. In this manner, the main server1802 can execute a series of processes to ensure safety and secureprocessing of information to meet federal privacy guidelines and thelike.

As also shown in FIG. 80, a system dashboard 8012 can be stored on themain server 1802. The system dashboard 8012 can form a structured memoryfor storing information received during execution of a process such asthe previously described processes. The system dashboard 8012 canfurther store documents, templates, applications, etc. for executing anyof the previously described processes.

The system dashboard 8012 may include a developer or resort dashboard8014 and an application dashboard 8016. Each of these dashboards will bedescribed in further detail below. To access each dashboard, the systemdashboard 8012 can be designed to restrict access to a limited number ofusers or seat licenses. Moreover, restricted access can also limit whatportions of each database a user or license may access. In this manner,certain restrictions may only allow a user or license read-only access,for example.

An example of the application dashboard 8816 is shown in FIG. 81. Inthis example, the application dashboard can be retrieved from the serverand displayed on a screen of an electronic computing device such that aplurality of information is displayed. For instance, the dashboard 8816can display information such as an application step 8100 for completinga transaction. The transaction, for example, can be a transfer of atimeshare interest or property.

The application step 8100 can include a plurality of steps 8110 forcompleting the transaction. For instance, the plurality of steps 8110can include a first step corresponding to a transfer applicationreceived, a second step corresponding to a transfer fee paymentinformation collected, a third step corresponding to manual datavalidation and clean up, a fourth step corresponding to resortverification received, a fifth step corresponding to title processingcompany selected, a sixth step corresponding assign order number, aseventh step corresponding to transfer fee charged, an eighth stepcorresponding to prepare documents, a ninth step corresponding to senddocuments, a tenth step corresponding to collect fees, an eleventh stepcorresponding to receive signed documents, a twelfth step correspondingto prepare final closing documents, a thirteenth step corresponding tosubmit final closing documents, and a fourteenth step corresponding toverify closing completion.

The dashboard 8816 can also display a number of applications pending8102 at each application step 8100. For instance, if the transactionincludes fourteen (14) steps, then the dashboard 8816 can display eachstep of the transaction and further identify how many applications arepending at each of the fourteen (14) steps. The dashboard display canfurther provide an option to view 8108 the pending applications for agiven step.

In addition, the application dashboard 8816 can also display a number ofapplications flagged 8104 and a number of applications completed 8106.In each case, an option to view 8108 is available to display theapplications flagged or completed at each application step 8100.

Although not shown in FIG. 81, the application dashboard 8016 canfurther provide means for displaying any pending application that wasstarted by a third party but has not yet been submitted to the serverfor processing. A similar option to view can allow for additionalinformation about each pending yet not submitted application to bedisplayed on the dashboard display. Moreover, the application dashboard8016 can display all open and closed applications stored on the mainserver 8002.

As described above, the application dashboard 8016 provides at least twodifferent sources of pending applications stored on the main server8002. The first source is the number of applications pending 8102. Thesecond source is pending applications that have been started by a thirdparty but not yet submitted for processing by the main server 8002. Thesecond source of pending applications may be stored on the server untilthe third party requests to continue executing a program to complete theapplication. Once completed, the application status changes from apending but not yet completed application to a pending application. Inany event, both of the two sources of pending applications are stored onthe server and may be displayed in a pending application dashboard 8200similar to that shown in FIG. 82. The pending application dashboard 8200can be a subset or part of the application dashboard 8016 similar to howthe application dashboard 8016 is part of the overall system dashboard8012.

In FIG. 82, one example of the pending application dashboard 8200 isshown schematically as it may be displayed on a screen of an electroniccomputing device. In this example, the pending application dashboard8200 can identify one or more applications pending at a certainapplication step 8100 of an overall transaction process (e.g., transferfee payment information collected). In FIG. 82, the application step canbe identified in block 8202. Besides identifying the application step,the dashboard 8200 can also display a plurality of information in block8204 related to the application. For example, in block 8204 thedashboard 8200 can display an application identification number, asubmission status (e.g., open, closed, pending, flagged, etc.), an ordernumber, processing status, processor, resort name or developer name,primary owner name, and other options. Among the other options is aprofile trigger displayed in block 8206 that can be selected to displayan application profile in block 8208. The application profile will bedescribed in further detail below.

Returning to FIG. 80, the main server 8002 stores a system dashboard8012 that can be accessed for displaying the application dashboard 8016or the developer or resort dashboard 8014. The developer or resortdashboard 8014 can display similar information as shown in block 8204 ofthe pending application dashboard 8200. Here, the developer or resortdashboard 8016 can display all applications stored on the server for aspecific developer or resort company. The dashboard 8016 may display aselectable option to the screen of the electronic computing devicewhereby a user can select a certain developer or resort company from alist of developer and resort companies. Once selected, only thoseapplications for the selected developer or resort company may bedisplayed on the dashboard screen. In this display, the applicationidentification number, developer name, resort company name, sellerinformation (e.g., seller name, email address, residential or businessaddress, phone number(s)), buyer information (e.g., buyer name, emailaddress, residential or business address, phone number(s)), andapplication date. The application date can identify the date upon whicheach application was submitted, received, etc. The dashboard 8016 canalso display a selectable option to access the application profile 8208of each individual application.

In FIG. 83, one embodiment of an application profile 8208 displayed in adeveloper or resort company application dashboard screen 8300 is shown.The application profile 8208 can be displayed on a screen of theelectronic computing device in the form of a plurality of blocks ofinformation. Information received from the different modules, e.g.,party information module, resort property module, documentation module,payment module, etc., can be stored on the main server 8002 in thesystem dashboard 8012. In a first block 8302, main information about theapplication is displayed. Here, information such as the applicationidentification number, order number, status, date submitted, useridentity that entered information, payment method, and paymentcompletion may be displayed in the first block 8302. In otherembodiments, additional or fewer information may be displayed here.

In a second block 8304, resort and/or unit information may be displayed.Here, information including developer name, resort company name, accountnumber, book information, page information, county information, buildingidentity, unit identity, and week identity may be displayed in thesecond block 8304. In a third block, transfer information such aspurpose of a transfer, transfer type, power of attorney, titleinsurance, use period, contract date, prior transfer date, and escrowinformation may be displayed in the application profile 8208.

The application profile 8208 may include a fourth block 8308 entitledbroker information. If there is no broker, then there may not be anyinformation displayed in the fourth block 8308. If a particularapplication is a broker application, information about the broker may bedisplayed in the fourth block 8308.

The application profile 8208 may include a fifth block 8310 entitledowner information and a sixth block 8312 entitled buyer information.Each block can include information received from the party informationmodule such as party name, email address, home phone number, and workphone number. Additional or fewer information may be included for eachparty in each block in alternative embodiments.

The application profile 8208 may also include a seventh block 8314entitled title information, an eighth block 8316 entitled feeinformation, a ninth block 8318 entitled notification information, and atenth block 8320 entitled title policy information. In the seventh block8314, title information may include vested buyer (e.g., joint tenants),vested seller, vested trust, request type (e.g., family gift), andtransfer price. In the eighth block 8316, fee information may includetransfer fee amount, current year maintenance fee amount due, previousyear maintenance fee amount due, current year club due amount, andprevious year club due amount. In the ninth block 8318, notificationinformation may include contact preference (e.g., email, mail, etc.) andadditional document(s) delivery preference. In the tenth block 8320,title policy information may include coverage, warranty type, date, daterecorded, book information, page information, number, and date issued.

Each block in the application profile 8208 provides a means for editingany information displayed therein. Thus, if a party submits anapplication and later identifies a mistake, this information can bemodified in the application profile by accessing the dashboard 8300 ofFIG. 83.

The application profile 8208 can be displayed such that each of theplurality of blocks is displayed. In addition to this information, theapplication profile 8208 can include a number of tabs displayed. Forexample, in FIG. 84, the plurality of tabs in the application profile8208 can include an owner and buyer information tab 8400, an uploads fortransaction tab 8402, a packages for transaction tab 8404, and a statusor timeline tab 8406. Each tab may display information that may also bedisplayed in one or more of the plurality of blocks shown in FIG. 83.Additional information, however, may also be displayed. For example, inthe owner and buyer information tab, information may be displayedincluding owner type (e.g., owner, buyer, etc.), party name, partyaddress, phone number(s), email address, marital status, relation,whether a party is being removed from a transaction, and additionaloptions. In the owner and buyer information tab, the server can displaywhether the party address for the buyer and owner has been verified byone of the third party servers associated with the postal service. Underthe additional options, the application profile 8208 can further providea means for modifying any of the information listed in the owner andbuyer information tab. Other options may be available as well.

Under the uploads tab 8402, documents that were uploaded to the server8002 for a given application may be identified by a filename ordescription, file type, verification, and options. Under the status ortimeline tab, each of the steps shown in the block 8110 in FIG. 81 maybe shown and the status of the application based on each step (e.g.,when a particular step was started, completed, etc.).

As also shown in FIG. 84, the application profile 8208 may include apackages for transaction tab 8404. Under this tab 8404, each documentthat is sent to each party of the transaction is shown and to whom thedocument was sent. Since a transaction for transferring timeshareproperty can require the parties of the transaction to execute one ormore documents to complete the transaction, the packages tab 8404includes a packages part 8408 that lists each document for a giventransaction. Here, the given transaction corresponds to a particularapplication that is shown and stored in the application profile 8208 onthe server 8002. Each transaction may have a package of documents thatare for one party, e.g., the owner of the timeshare property, andanother package of documents that are for another party, e.g., the buyerof the property. Some documents may be similar for both parties, whereascertain documents may only be in the owner package and other documentsare only in the buyer package. The package parts 8408 displays eachdocument that is part of a given package, and each document may beopened on a different server for viewing.

In some applications, a particular developer or resort company mayrequire one or more documents to be communicated to a party of atransaction. The one or more documents therefore is included in thepackage parts for that party. The application profile 8208 also providesadditional options as well. For example, a first option includes addinga new template document 8410 from the template library 8020 to thepackage parts 8408. A second option includes upload a document to thepackage 8412 from another server. A third option includes to transferthe package parts to the parties 8414. Under the third option, theserver is instructed to transfer the buyer package parts to the buyeremail address, for example, and the owner package parts to the owneremail address. Additional options may be available as well, such as anoption to download a PDF file of the package parts or one or moredocuments of the package parts.

As described, the server 8002 can store a plurality of documents fortransferring a timeshare interest or property between two parties. Forany given transaction, a package can be formed such that it includes oneor more the plurality of documents stored on the server 8002. Thus, whenan instruction is received by the server 8002 from a third party serverto execute a certain process for a given transaction, the server 8002can execute the instruction by forming the necessary package ofdocuments with the ability to transfer the package of documents toanother server for access by a third party. Some development and resortcompanies require certain packages that include a number of differentdocuments for a party in a given transaction. Moreover, while the serveris capable to forming a package of documents for any given transactionfor any particular development company or resort company, the server isalso capable of creating or modifying any package of documents. Anexample of how the server can form a package of documents is shown inFIG. 85.

Referring to FIG. 85, a process 8500 for adding a package for any giventransaction is shown. The process 8500 can take the form of an add apackage module 8502 or algorithm stored on the server 8002. The module8502 can be executed by a user on a third party server such as aprocessor 8504 or developer/resort company 8516. The processor servermay be a party that manages the information stored on the server, forexample.

The processor server can execute the add a package module 8502 on theirserver by first logging into the system dashboard 8012. The module 8502can be executed according to a first block 8506 by accessing anapplication profile for a corresponding developer/resort application,e.g., an application for transferring a developer's or resort'stimeshare property. A second block 8508 of the module 8502 can beexecuted by accessing the packages option or tab on the applicationprofile 8208 for the corresponding application.

A third block 8510 of the add a package module 8502 can be executed bythe third party server by instructing the main server 8002 to add atemplate to the package parts. This may be for one or both parties ofthe transaction. Once the server executes this instruction, the servercan communicate an add template form to the third party server. The addtemplate form can display a list of all templates associated for thespecific developer or resort company that are stored in the templatelibrary 8020 in the database 8018, or it may include all templates forall developer and resort companies. The list of templates does notinclude templates for other developer or resort companies. Thus, afourth block 8512 may be executed by the third party server upon theselection of a template associated with the developer or resort companyfrom the template library 8020.

Once the fourth block 8512 is executed, an instruction is sent to themain server 8002 to add the selected template to the package parts forthe given party package (e.g., buyer package, owner package). The mainserver 8002 can then communicate with the database 8018 to receive theselected template therefrom and place the selected template into thepackage parts 8408. In this way, a new package is created for aparticular development or resort company by adding a template associatedwith only that development or resort company to a package.

On the processor side 8516, a different block 8518 may be executed aspart of the add a package module 8502 by the processor server. In thisblock, the processor server can send an instruction to the main server8002 to select a site from a list of sites stored on the server 8002.This may, for example, be an instruction to select “Owner to Owner”,“Hold My Escrow”, “Request My Estoppel”, or “Jiffy Doc”, each of whichis a different site stored on the server 8002. Upon selection of a site,the main server 8002 communicates a different display in the form ofblock 8520 whereby the third party server is requested to select aparticular resort or developer profile. The third party server cancommunicate an instruction associated with the particular resort ordeveloper profile to the main server 8002.

The next block 8522 in the add a package module can be executed upon theselection of a processor for handling the particular transactions of agiven developer or resort company. For clarity sake, the processor inthis case is a third party that may manage and facilitate theaforementioned processes. Here, an instruction can be communicated tothe main server from the third party server to retrieve profileinformation of the processor for the transaction. The processor canoperate on the third party server and thus communicate in a reciprocalmanner with the main server 8002.

The main server 8002 can store a plurality of standard packages or itcan request the standard packages from the database 8018. These standardpackages are likely ones created by the processor and stored by theprocessor on the main server 8002 or database 8018. In any event, theplurality of standard packages can be communicated from the main server8002 to the third party server in block 8524 so that the third partyserver can further execute the module 8502 by modifying an existingstandard package or adding a new package to the plurality of standardpackages in block 8526.

In FIG. 86, block 8526 is further described with respect to a bilateralapproach. Stated another way, block 8526 can be executed to modify anexisting package stored on the server or in the database, or add a newpackage to be stored on the server or in the database. For instance, amethod for modifying an existing package of transfer documents stored onthe server or in the database can be executed beginning in block 8600via communication between the main server 1802 and a third party serverassociated with a processing company, i.e., the processor of thetransfer. To do so, block 8602 in FIG. 86 can be executed by accessingan existing package from the database 8018 or main server 8002. Here,the processing company sends an instruction from its server to the mainserver to request access to an existing package. The instruction caninclude details about the type or filename, for example, of the desiredexisting package.

Once the server 8002 receives this instruction from the processorserver, the main server 8002 either obtains the package from the serveror the database 8018. The package can include one or more templates thatform part of the package. For instance, a standard seller package mayinclude the following templates: Welcome Letter, File Cover Page, FileChecklist, Third Party Transaction Agreement, Compliance and CorrectionAgreement, Resort Transfer Form, Contract, Seller Affidavit,Authorization to Release, Owner Affidavit, and W-9 Form. A standardbuyer package may include a similar list of templates. As describedabove, each template may include one or more identifiers. Upon receivinginput data, the main server 8002 link or merge the input data with theone or more identifiers in each template to complete the template withthe input data. As a result, the main server 8002 can produce titletransfer documents or any other type of document from the package oftemplates stored on the server or in the database.

Once the existing package is therefore located by the server 8002, block8604 of the process can be further executed by the main server 8002 bycommunicating the list of templates associated with the existingpackage. The list of templates may be displayed on a screen of anelectronic computing device of the processing company such that adetermination can be made whether the list of templates is complete orwhether the package needs to be modified for a given transaction.

In block 8606, the server can also communicate at least two options tothe processor server. First, one or more of the templates that make upthe existing package may be deleted or removed from the package, orsecond a new template may be added to the package. Another option mayinclude to delete or remove the package altogether.

If the processing company desires to add a new template to the existingpackage, however, in block 8608 the processor server can communicationto the main server 8002 an instruction to add a new template from thedatabase 8018 or server 8002 to the existing package, i.e., add apre-existing template to the package. In turn, the server 8002 cancommunicate a list of all pre-existing templates to the processingserver for display on the screen of the device belonging to theprocessing company.

The processing company can select the template or templates to add tothe existing package by communicating this information from theprocessor server to the main server 8002. Once the server 8002 receivesthis instruction from the processor server, the server 8002 in block8610 and update the existing package by adding the new template ortemplates thereto and storing the updated package either on the server8002 or in the database 8018. The previously described process is onlyintended to be an example, and alternative processes may includeadditional or fewer steps from beginning to end.

The processing company may also desire to add an entirely new package ofdocuments for storing on the server 8002 or in the database 8018. To doso, such a process can be executed at block 8612. Here, the processorserver can send an instruction to the main server 8002 in block 8614 toaccess existing packages from the server 8002 or database 8018. Thesubstance of block 8614 can be executed in a similar manner as block8602. Upon receiving this instruction from the processor server, themain server 8002 can retrieve the existing packages from the server ordatabase. The server 8002 can communicate the list of existing packagesto the processor server for further display to the processing companyvia an electronic computing device.

In addition to a list of existing packages, in block 8616 the server8002 may also communicate an option to add a new package to the existingpackages. If this is desirable, the processing company can communicatethis to the server 8002 via the processor server. Once this instructionis received by the main server 8002, the main server 8002 can request aname for the new package in accordance with block 8618. This request canbe communicated to the processor server, where the processing companymay enter the name of the new package. For purposes of this embodiment,the processing company may enter “New Package” as the name of the newpackage. This can be communicated back to the main server 8002.

The main server 8002 can then send another communication to theprocessor server with a number of options. For example, one of theoptions may be to delete “New Package”. Another option may be to edit ormodify the name of “New Package”. A third option may be to edit or add atemplate to “New Package”. Assuming the processing company desires toadd a template to “New Package”, an instruction may be sent to mainserver 8002 communicating this desire. In block 8620, the server 8002therefore receives an instruction to edit the template list of “NewPackage”.

The server 8002 can then send a request to the processor server in block8622 indicative of an option to add an existing template from thetemplate library 8020 to “New Package”. The processing company canselect this option, and upon selecting this option, an instruction canbe sent to the main server 8002 that the processing company wants to addan existing template to the “New Package”. Upon receiving thisinstruction, the main server 8002 can execute block 8608, for example,and provide a list of the existing templates stored in the templatelibrary to the processor server. In block 8624, the processor server cancommunicate one or more existing templates to be added to “New Package”.Upon receiving this instruction from the processor server, the mainserver 8002 in block 8610 can store the one or more existing templatesin the “New Package” and store the entirety of “New Package” on theserver 8002 or database 8018 for later use.

The above process describes at least one example of how an existingpackage can be modified such that a template is either removed from oradded to the package. Moreover, the above process also describes aprocess for adding a new package and adding existing templates to thenew package. The processes are described only as examples, and oneskilled in the art should appreciate that other steps or processes maybe executed for modifying an existing package stored on the server ordatabase or adding a new package.

Referring to FIG. 87, a different process 8700 is shown for creating anew template. The process 8700 includes a block 8702 for executing acreate a new template module. A processing company that manages thetemplate library 8020 and the packages of documents stored on the mainserver 8002 or database 8018 can execute the process 8700 by sending aninstruction from its processor server to the main server 8002. The mainserver 8002 can receive the instruction to display all existingtemplates stored in the template library 8020. In turn, the server 8002can transfer a list of existing templates stored in the template library8020 to the processor server for display on a screen of an electroniccomputing device.

In block 8706, an option may also be displayed on the screen of thedevice to download an existing template or add a new template. To add anew template, the processor server sends an instruction to the mainserver 8002 indicative of creating a new template. The main server 8002can retrieve a system template form from the database 8018 or the serveritself, and can then send electronically the system template form to theprocessor server. In block 8708, the system template form can bedisplayed on a screen of the computing device so that the processingcompany can begin creating a new template name. For purposes of thisembodiment, the new template name will be referred to as “New Template”.The processor server can send an electronic communication to the mainserver 8002 in which the communication includes the new template name“New Template”.

In block 8710, the main server 8002 can create a file entitled “NewTemplate” and store it in the template library 8020. The file “NewTemplate” may be an empty file at this time, but it is created andstored in the template library. In addition to storing the file in thetemplate library, the server 8002 can send an instruction to theprocessor server to provide an option in block 8712 to upload a filefrom the processor server. In addition to the option, an instruction mayalso be provided by the main server corresponding to “New Template”. Forexample, the instruction may advise the processor that the file namestored on the processor server must be identical to the file name “NewTemplate” as stored in the template library 8020.

In block 8714, the processor server can send an instruction to the mainserver to upload and link a file on the processor server to the “NewTemplate” stored in the template library. In addition to theinstruction, the processor server may send the file to the main server8002 as well. Once the main server 8002 receives the instruction andfile in block 8714, the main server may execute block 8716 to determineif the file name corresponding to the file sent by the processor serveris identical to the template name “New Template” stored in the templatelibrary 8020. If the file name is identical to “New Template”, then theprocess 8700 can advance to block 8718. If not, the server 8002 can senda message to the processor server for display on the screen of thedevice that the file name and new template name “New Template” are notidentical. Process 8700 cannot advance to block 8718 until the file namematches the template name “New Template”.

Once the file name and new template name match, the process 8700 canadvance to block 8718 such that the main server 8002 can store the fileunder the name “New Template” in the template library 8020. Once the newtemplate is stored in the template library 8020, the new templatebecomes one of a plurality of templates stored in the library. Moreover,existing packages can be modified according to the processes describedabove to add the new template, or new packages can be created to includethe new template. The new template can be used to create a new documentrequired for a particular transaction, where the template may include atleast one identifier to be linked to input data received by the mainserver during execution of the one of the processes described above.While the process 8700 of FIG. 87 describes one way to create a newtemplate, it should be appreciated that other steps or methods may beused to create similar files for use in a transaction.

While exemplary embodiments incorporating the principles of the presentdisclosure have been disclosed hereinabove, the present disclosure isnot limited to the disclosed embodiments. Instead, this application isintended to cover any variations, uses, or adaptations of the disclosureusing its general principles. Further, this application is intended tocover such departures from the present disclosure as come within knownor customary practice in the art to which this disclosure pertains andwhich fall within the limits of the appended claims.

1. A method for modifying a package of documents for transferring atimeshare property, comprising: providing a first server disposed inelectrical communication with a second server and a database, the firstserver and second server arranged so that instructions are transferabletherebetween for a plurality of operations, and the second serverelectrically coupled to a computing device including a processor and adisplay screen; providing a template library electronically stored onthe database; storing a first plurality of templates in the templatelibrary; receiving by the first server a first instruction from thesecond server to access an application profile for a particulardeveloper or resort company of timeshare properties; receiving by thefirst server a second instruction from the second server to add atemplate to a package stored on the first server or database, thepackage including one or more templates from the first plurality oftemplates; sending a list of the first plurality of templates by thefirst server to the second server; receiving by the first server fromthe second server a third instruction associated with a selection of atleast one of the first plurality of templates; modifying the package bythe first server to include the at least one selected template from thefirst plurality of templates to the package, wherein the packagecomprises a second plurality of templates after the modifying step; andsending the modified package by the first server to the second server,wherein the package of the second plurality of templates are executableto produce a package of documents for transferring the timeshareproperty.
 2. The method of claim 1, wherein at least one of the firstplurality of templates comprises an identifier.
 3. The method of claim1, further comprising receiving a fourth instruction by the first serverfrom the second server corresponding to an identification of a developeror resort company site.
 4. The method of claim 1, further comprisingreceiving a fourth instruction by the first server from the secondserver corresponding to an identification of a title processing company.5. The method of claim 4, further comprising accessing by the firstserver a plurality of standard packages stored on the first server,second server, or the database.
 6. The method of claim 5, wherein theplurality of standard packages comprises a third plurality of templates,the third plurality of templates being executable to produce one or moredocuments for transferring the timeshare property.
 7. A method ofproducing a package of documents for transferring a timeshare property,comprising: providing a first server disposed in electricalcommunication with a second server and a database, the first server andsecond server arranged so that instructions are transferabletherebetween for a plurality of operations; providing a template libraryelectrically stored on the database; storing a first plurality oftemplates in the template library and a plurality of packages on thefirst server or the database; receiving by the first server a firstinstruction from the second server to add a new package to the pluralityof packages; sending by the first server to the second server a requestfor a new package name; receiving by the first server the new packagename from the second server; receiving by the first server a secondinstruction from the second server to edit a template list of the newpackage; sending by the first server to the second server a list of thefirst plurality of templates for adding to the new package; receiving bythe first server a third instruction from the second server to add atleast one of the first plurality of templates to the new package; andstoring the new package with the at least one of the first plurality oftemplates added thereto on the first server or the database.
 8. Themethod of claim 7, further comprising receiving by the first server afourth instruction from the second server to retrieve the plurality ofpackages from the database.
 9. The method of claim 8, further comprisingaccessing by the first server the plurality of packages from thedatabase.
 10. The method of claim 7, further comprising sending a fourthinstruction by the first server to the second server, where the fourthinstruction corresponds to an option to remove one template of the firstplurality of templates from the database.
 11. A method of producing atemplate for a document to transfer a timeshare property, comprising:providing a first server disposed in electrical communication with asecond server and a database, the first server and second serverarranged so that instructions are transferrable therebetween for aplurality of operations; providing a template library electricallystored on the database; storing a first plurality of templates in thetemplate library and a plurality of packages on the first server or thedatabase; receiving by the first server a first instruction from thesecond server to execute a new template module; sending by the firstserver to the second server a list of the first plurality of templatesand an option to add a new template or download one of the plurality offirst templates; receiving by the first server from the second server anew template name for adding a new template to the first plurality oftemplates; receiving by the first server a second instruction from thesecond server to upload a file associated with the new template name,the file being stored on the second server; determining if the fileincludes a file name identical to the new template name; uploading thefile if the file name is identical to the new template name; and storingthe file so that a second plurality of templates are stored in thedatabase.
 12. The method of claim 11, further comprising storing thefile in the template library.
 13. The method of claim 11, furthercomprising sending a third instruction by the first server to the secondserver where the third instruction corresponds to a template form. 14.The method of claim 13, wherein the template form comprises a requestfor a new template name.
 15. The method of claim 11, further comprisingstoring the new template name in the template library before the secondinstruction is received by the first server.
 16. The method of claim 11,further comprising sending a third instruction by the first server tothe second server corresponding to an option to upload a file associatedwith the new template name.
 17. The method of claim 11, furthercomprising receiving by the first server a third instruction from thesecond server to add a template to a package stored on the first serveror database, the package including one or more templates from the secondplurality of templates.
 18. The method of claim 17, further comprising:sending a list of the second plurality of templates by the first serverto the second server; and receiving by the first server from the secondserver a fourth instruction associated with a selection of at least oneof the second plurality of templates.
 19. The method of claim 18,further comprising modifying the package by the first server to includethe at least one selected template from the second plurality oftemplates to the package.
 20. The method of claim 19, further comprisingsending the modified package by the first server to the second server,wherein the package includes a third plurality of templates which areconfigurable to produce a package of documents for transferring thetimeshare property.